Asynchronous Payments

In an asynchronous workflow a redirection takes place to allow the account holder to complete/verify the payment. After this the account holder is redirected back to the app and the status of the payment can be queried.

This article will guide you how to support communication between apps for the asynchronous payment methods.

NOTE: If you have multiple app targets, be sure to add the return URL type for all of the targets.

Shopper result URL

Make sure that you send valid shopper result URL in the prepare checkout request. This URL will be opened after user passes verification or completes payment in another app (no matter successfully or not).

URL scheme should be the same that you've registered in the previous step. The rest part of URL can be any valid string (but not empty). For example, com.companyname.appname.payments://test

Update your application delegate

Then, in order to finalize the step, in your application delegate you need to process the payment authorization URL.
Make sure that URL scheme is identical to the registered one in previous step. Then send notification to request payment status and display result to the customer.