payment-gateway | Networking library

This error seems to be the result of using the VPSTxId as your threeDSSessionData value. I had the same issue but was able to resolve it by changing my threeDSSessionData to use a local transaction ID from my database instead of SagePay's one.

Another thing I noted was that while using the VPSTxId as the threeDSSessionData, the 3DS challenge simulator wasn't actually being displayed during the 3DS flow. As soon as I switched to using my own transaction ID it kicked back in.

You can use coordinators to manage the view controllers, and that coordinator will RazorpayPaymentCompletionProtocol.

Example:

Can I manage in-app purchases outside of the Microsoft Store, meaning using my own payment-gateway like stripe.com ?

Yes, based on the Store policy 10.8 Financial Transactions, Non-game in-app products made available on PC devices may either use a secure third-party purchase API or the Microsoft Store in-product purchase API for in-app purchases of digital items or services that are consumed or used within the product.

if yes are there any sample example or article on the same.

No, there is no sample about using third-party purchase API. You need to check the document of these third-party purchase APIs.

Can I implement in-app purchases with a custom price for each customer? for few customers we might want to give some varying discount. any sample example or article on the same?

If you are using third-party purchase APIs, then this will be an issue that you need to check the third-party purchase API document.

For Microsoft Store in-product purchase API, there is no such function that provides a custom price for every customer. What you could do is that having different add-ons with different prices in the Microsoft Store. Then for different customers, you show the different add-ons.

The only time sum has the value of 0 is when the .ready() function is fired. Every time the updateCheckout() function is fired you only add to sum and never subtract from it.

What you need to do is set sum=0; at the very beginning of that function so that every thing gets completely recalculated every time.

First, you have to log your @Input() identifier:string=""; in OnChanges() to be sure that you get the value each time when it's changes.

Seconds, can you show exactly where you emitted to your parent component ?

When calling create charge/subscription you should pass the price that the user paid. So #1 is the correct approach.

Source: I am currently helping the Corrily team with their documentation. This answer is what the Corrily engineering team told a customer to do.

With that EC API, when the buyer returns to your site, you are expected to display a final order review page for which the final approval action will then trigger the DoExpressCheckoutPayment API call (using the EC token and PayerID from the url query string that was returned with) to create a PayPal transaction. Based on the response you are to display a thank you/success message--or error message about not being able to process the payment. No transaction is created until you call DoExpressCheckoutPayment.

Regardless, this integration you are attempting is with the classic EC API which is several generations old (about 15 years old). You should not be using this old API for any new integration, that guide you are following is quite old and should be disregarded.

Instead, follow the current Set up standard payments guide and make 2 routes on your server, one for 'Create Order' and one for 'Capture Order', documented here. Both routes should return only JSON data (no HTML or text). Inside the 2nd route, when the capture API is successful you should store its resulting payment details in your database (particularly purchase_units[0].payments.captures[0].id, which is the PayPal transaction ID) and perform any necessary business logic (such as sending confirmation emails or reserving product) immediately before forwarding your return JSON to the frontend caller.

Pair those 2 routes with the frontend approval flow: https://developer.paypal.com/demo/checkout/#/pattern/server

Try checking the capitalization of your import. You should rename use stripe; to use Stripe;.

If you did install the package using composer require stripe/stripe-php, try running composer dump-autoload. This will regenerate the list of all classes that need to be included in your project. That will probably pick up the newly installed package.

You're assigning null to _upiAddrError but it's a non-nullable String.

Declare that variable as String? _upiAddrError instead of String _upiAddrError to make it nullable.