Skip to main content

Wallet Pay S2S

Private Beta Notice

The Apple Pay and Google Pay APIs described in this section are part of a private beta program. These endpoints may be subject to changes and are not yet available for general use. If you are interested in joining the beta, please reach out to your SysPay account manager.

Limitation: MIT and card token registration are not supported for Apple Pay and Google Pay​

Apple Pay and Google Pay currently support one-off, shopper-initiated payments only. Mandate registration, card tokenisation and merchant-initiated transactions (MIT) are not available for these payment methods at this stage.

For this reason, Apple Pay and Google Pay are automatically filtered out of the Hosted Payment Page whenever mandate = true is sent in the request. The wallets are only displayed when mandate = false.

Concretely, this means:

CapabilityCardsApple Pay / Google Pay
One-off shopper-initiated paymentSupportedSupported
Mandate registrationSupportedNot supported
Card token registration for later reuseSupportedNot supported
Merchant-initiated transaction (MIT)SupportedNot supported

Integration impact​

  • Any use case requiring a stored credential (subscriptions, recurring billing, deferred payments, one-click checkout, split or delayed captures) must be routed with mandate = true, and will therefore be processed with card payment methods only.
  • On the Hosted Payment Page, no error is returned when mandate = true is sent: the wallets are silently removed from the list of available payment methods. The merchant should not expect Apple Pay or Google Pay to appear in these flows.
  • On the Wallet Pay S2S API, mandate must be false or omitted; sending true returns error code 10007.
  • Merchants offering both one-off and recurring purchases should set the parameter dynamically per transaction, so that wallets remain available on the one-off flows.