Accept an Afterpay or Clearpay payment

You can optionally accept line item data to provide more risk signals to Afterpay. This feature is currently in private beta. Please contact us if you want to request access.

Unlike separate authorisation and capture for card payments, Afterpay charges the customer the first instalment of the payment at the time of authorisation. You then have up to 13 days after authorisation to capture the rest of the payment. If you don’t capture the payment in this window, the customer receives a refund of the first instalment, and they aren’t charged for any further instalments. In these cases, Stripe also cancels the PaymentIntent and sends a payment_intent.canceled event.

If you know that you can’t capture the payment, we recommend cancelling the PaymentIntent instead of waiting for the 13-day window to elapse. Proactively cancelling the PaymentIntent immediately refunds the first instalment to your customer, avoiding any confusion about charges on their statement.

Tell Stripe to authorize only

To indicate that you want separate authorisation and capture, set capture_method to manual when creating the PaymentIntent. This parameter instructs Stripe to only authorise the amount on the customer’s Afterpay account.

Upon authorisation success, Stripe sends a payment_intent.amount_capturable_updated event. Check out our Events guide for how it may help.

Capture the funds

After the authorisation succeeds, the PaymentIntent status transitions to requires_capture. To capture the authorised funds, make a PaymentIntent capture request. The total authorised amount is captured by default – you can’t capture more than this, but you can capture less.

Optional Cancel the authorisation

If you need to cancel an authorisation, you can cancel the PaymentIntent.

We recommend relying on Stripe.js to handle Afterpay redirects and payments client-side with confirmAfterpayClearpayPayment. Using Stripe.js helps extend your integration to other payment methods. However, you can also manually redirect your customers on your server by following these steps:

1. Create and confirm a PaymentIntent of type afterpay_clearpay. You must provide the payment_method_data.billing_details property that is required by Afterpay. payment_intent.shipping is optional but recommended for improved authentication rates. By specifying payment_method_data, Stripe creates a PaymentMethod and immediately uses it with this PaymentIntent.

   You must also provide the redirect URL for your customer after they complete their payment in the return_url field. You can also provide your own query parameters in this URL. These parameters are included in the final URL upon completing the redirect flow.

   The created PaymentIntent has a status of requires_action and the type for next_action is redirect_to_url.

2. Redirect the customer to the URL provided in the next_action.redirect_to_url.url property. The code example here is approximate—the redirect method may be different in your web framework.

When the customer finishes the payment process, they’re sent to the return_url configured in step 1. The payment_intent and payment_intent_client_secret URL query parameters are included and you can pass through your own query parameters, as described above.

We recommend that you rely on webhooks to confirm the status of a payment.

Stripe sends a payment_intent.succeeded event when the payment completes. Use the Dashboard, a custom webhook, or a partner solution to receive these events and run actions, like sending an order confirmation email to your customer, logging the sale in a database, or starting a shipping workflow.

Listen for these events rather than waiting on a callback from the client. On the client, the customer could close the browser window or quit the app before the callback executes, and malicious clients could manipulate the response. Setting up your integration to listen for asynchronous events also helps you accept more payment methods in the future. Learn about the differences between all supported payment methods.

• Handle events manually in the Dashboard

  Use the Dashboard to View your test payments in the Dashboard, send email receipts, handle payouts or retry failed payments.

• Build a custom webhook

  Build a custom webhook handler to listen for events and build custom asynchronous payment flows. Test and debug your webhook integration locally with the Stripe CLI.

• Integrate a prebuilt app

  Handle common business events, such as automation or marketing and sales, by integrating a partner application.

Test your Afterpay integration with your test API keys by viewing the redirect page. You can test the successful payment case by authenticating the payment on the redirect page. The PaymentIntent will transition from requires_action to succeeded.

To test the case where the user fails to authenticate, use your test API keys and view the redirect page. On the redirect page, click Fail test payment. The PaymentIntent will transition from requires_action to requires_payment_method.

For manual capture PaymentIntents in testmode, the uncaptured PaymentIntent will auto-expire 10 minutes after successful authorization.

The Payment Method Messaging Element is an embeddable UI component that helps your customers know which buy now, pay later payment options they have at checkout directly from your product, cart, or payment pages.

To add the Payment Method Messaging Element to your website, see Display payment method messaging.

United States (USD)

Payment Methods

US$99.00

The Making of Prince of Persia: Journals 1985-1993

Jordan Mechner

US$99.00