Web Redirect on Android
With Web Redirect, your server creates a checkout and returns its redirect URL to your app. The SDK loads the URL in a web view and watches for the redirect to your confirm or cancel URL. When the customer confirms, the SDK returns the order token, and your server completes the payment.
Web Redirect is the simplest way to present checkout. The SDK calls it Checkout V1.
Step 1: Create a checkout on your server
When the customer starts checkout, your server calls Create Checkout and returns the redirectCheckoutUrl from the response to your app.
Set both merchant.redirectConfirmUrl and merchant.redirectCancelUrl. The SDK uses them to detect the result. They can be any URLs; by default, the SDK doesn’t load them.
Step 2: Start the checkout
Register an activity result launcher, then launch the intent from createCheckoutIntent with the checkout URL. The SDK checks that the URL is an Afterpay checkout URL before it loads it.
Load the redirect URLs
By default, the SDK stops at the redirect and doesn’t load your confirm or cancel URL. To let the redirect URL load and read the result when it starts loading, pass loadRedirectUrls = true to createCheckoutIntent.
Step 3: Handle the result
parseCheckoutSuccessResponse returns the order token. parseCheckoutCancellationResponse returns a CancellationStatus:
Step 4: Complete the order
Send the order token to your server. To capture the full amount immediately, your server calls Capture Full Payment with the token. To capture later, call Auth and then Capture Payment.
For the full server flow, see the Mobile SDK quickstart.