Skip to main content

​
Available methods

Two payment methods are available: Apple Pay and PayPal. Both are available in the UK and US. Apple Pay supports Individual accounts, while PayPal supports both Individual and Business accounts. Support for Business accounts on Apple Pay, and more methods, will be added soon.

​
Coverage

​
Supported features

​
Browser and platform compatibility (Payment Widget)

Some APMs require authorization through the Payment Widget regardless of integration path, whether via REST API or via the widget directly. ¹Partial support — Apple Pay renders a QR code instead of the payment sheet; the user must scan it with an iOS device to complete the payment there. Withdrawals not supported at this moment.

​
Apple Pay

Apple Pay requires a couple of extra things to be set up:
  • Domain registration — For web apps, your top-level domain must be registered with Apple Pay before going live (this is not necessary for sandbox if you use an Apple Tester Account as explained here). Contact your account manager if you haven’t done so already, and note that:
    • Your domain must not already be registered with a different Apple Merchant ID in the Apple Developer Portal.
    • You must verify ownership of your domain by hosting a domain verification file, which we provide.
  • Native apps — integrating with the Payment Widget without the SDK works out of the box. If you use the Web SDK instead, the WebView’s HTML page must be served from a real HTTPS origin rather than bundled locally.

​
Key concepts

  • Transfers are quote-based — deposits and withdrawals both require the user to confirm a quote before the transaction is created, whether funds are being collected from the payment method or paid out to it.
  • APM authorization — when the quote response includes a authorize:<method> requirement, the specified method needs to be authorized. Use the Payment Widget to manage the authorization flow.
  • Authorized external accounts — some APMs support account linking. After the first deposit or withdrawal, an external account is created and reused automatically for subsequent transactions. Other APMs don’t support linking, so the transaction node is always the APM identified by its method, with no persistent external account created.

​
Testing in Sandbox

Each APM has its own setup for testing in Sandbox. See Testing APMs for testing steps and recommended actions to take.

​
Start building

Deposit via API

Fund a user’s account programmatically.

Deposit via Widget

Let users deposit funds with a low-code, embeddable widget.

Withdrawal via API

Create quotes and submit payouts programmatically.

Withdrawal via Widget

Let users withdraw funds with a low-code, embeddable widget.