alipay | alipay api for laravel | REST library

Error via Google Translate: '签名字段异常' -> 'Signature field exception'

1. Validate the signature. Replace $privateKey and $publicKey from you secrets.

First increase the connection timeout, you currently have it set to 4 seconds, the default is 30 seconds. Because test.mosquitto.org is a totally public broker it often gets hammered by people (either testing stuff or just not thinking what they are doing) so a longer timeout is better.

Secondly, having a clientID of test_client is VERY likely to clash with another client so your client will get kicked off the broker as soon as the other client tries to reconnect which will cause your client to reconnect causing a connect/disconnect loop. ClientID's need to unique across ALL clients connecting to the broker, I suggest you change this to a unique to you prefix combined with a random number.

Thirdly you don't actually do anything even if you connect, you make no subscriptions, so the on message event handler will never be called. You don't even have a on connect event handler to know if you ever get connected cleanly.

e.g.

previously FPX wasn't available in the Payment Element, but it is now. You can see supported payment methods here.

Stripe doesn't support that kind of automatic currency conversion today, no.

If you want to charge customers in different locations in different currencies, then you have to tell Stripe to charge an amount X in currency Y based on your own specific business logic.

If using Checkout, the idea is you would create a Product and can define various Prices in different currencies , https://stripe.com/docs/billing/prices-guide . The amount you use for the local currency is something you as the merchant decide when setting this up. So yes, as you describe, you want to create a new Price for their country/currency combo.

More generally I want to point out that you probably don’t want to just do a straight conversion, you want to actually consciously price your product according to local competitors and purchase power like the Big Mac Index. If you Google “price localisation” there’s lots of blogs about this kind of thing. For example $50 is about 3,600INR, but the average monthly salary in India is (taking a random example from Google), 16,000INR. So that "$50" item is a much more expensive proposition to your Indian customer in that country if you just do straight conversions instead of consciously pricing your product.

You cant get videos to play in native mini programs because the tag is not currently supported.

You could get videos to play by making use of the web-view which points to a website which hosts the video

The URL https://[app-id].hybrid.alipay-eco.com is for the Referer for the simulator.

The URL https://[app-id].sass.mini-program.com is the referrer being used in production. In both cases is the App ID set by VodaPay.

However, if you preview the app on the device (i.e. a dev build from the simulator that is only valid for 15 min) no Referer header is sent.

line_items are no longer included by default when retrieving Checkout Sessions. To get them in your retrieve call, you need to expand the line_item property.

You have two syntax errors : You're missing a layer and using dot notation instead of PHP arrow syntax. The 2nd error is using $session instead of $checkout_session. So it should be :

$quantity = $checkout_session->line_items->data[0]->quantity;

It's not possible to do that - you can only set one currency for the Checkout Session.

The flow you are describing is used when you want to have a customer and a card on the platform account and then clone that card on the connected account to accept a one-time payment. The idea is that as a platform you collect card details once and can accept future payments on behalf of third-party vendors for example.

The customer in the platform and the one on the connected account are not related or linked in any way when you do this. They are just 2 separate objects and you would be able to clone the card once to avoid collecting the card details again.

In your example though you don't have a card nor do you want to collect one. This means there's no reason to create a customer on the platform account or try to clone it on the connected account. You seem to only want to accept a payment on the connected account.

You should skip all the steps entirely and instead just create a Checkout Session on the connected account. As you go through Checkout it will collect card details, accept the payment and also create a Customer for you on the connected account to save the card details for future payments.

You won't be able to use that customer on the platform nor its card, but that part is expected with the way Stripe Connect is built.