Digital wallets

Use a real enrolled card and sandbox amount codes to trigger Click to Pay, Apple Pay, and Google Pay outcomes. Click an amount to copy it.

Click to Pay

You can test Guide
Integrate Click to Pay into your payment form to let customers complete checkout using saved card credentials from major card networks without re-entering payment details. Click to Pay on the payment form through a sandbox PSP without charging real funds. The Click to Pay integration itself and its credentials are live.

Before starting tests, contact us to discuss configuration needs. Keep in mind that Click to Pay requires real cards and an active Click to Pay account, the same as Apple Pay and Google Pay. Sandbox test cards from this documentation do not work. Successful payments through the sandbox PSP do not debit funds.

Use accessible real email addresses and phone numbers for Click to Pay authentication. The live Click to Pay service requires a valid one-time password (OTP) sent to one of these contacts.

To display Click to Pay on the payment form, pass clickToPayButtonParams during form initialization:

1
2
3
4
5
6

clickToPayButtonParams: {
  enabled: true,
  saveRecognitionToken: true, // stores the token for 180 days
  supportedCardNetworks: ["visa", "mastercard"],
  height: 56, // value between 52 and 60
},

The Click to Pay button is always rendered above the card form. The card form must remain visible alongside Click to Pay, as required by card schemes. For layout rules, events, and full parameter details.

To simulate payment outcomes, use a real card enrolled in Click to Pay and set amount in cents to the same values as for Apple Pay or Google Pay:

• 100 for success without 3DS
• 666 for success with 3DS challenge
• 555 for success with frictionless 3DS

Apple Pay or Google Pay

Sandbox provides a secure environment for simulating the integration of Guide
Add a Google Pay button to your embedded payment form for one-tap checkout on Android devices and Chrome browsers with token security. Google Pay and Guide
Add an Apple Pay button to your embedded payment form for one-tap checkout with biometric authentication on supported Apple devices. Apple Pay, without any risk to real bank accounts or transactions.

For the initial one-time payment, using an amount that is not listed below results in a standard approval. This ensures that all subsequent recurring payments using the same token are automatically approved. However, to trigger specific recurring or recurring auth payment outcomes, the initial transaction must use predefined amount values, which should be specified in cents. For example, an amount of 100 represents 1.00. Use the following values:

• 100 for Guide
  3D Secure enhances online payment security by verifying cardholder identity, reducing fraud, and shifting liability from merchants to card issuers. no 3DS success
• 666 for Guide
  Challenge flow in 3D Secure 2 requires cardholder interaction for authentication, triggered by high-risk scenarios or regulatory mandates. challenge success
• 555 for Guide
  Frictionless flow in 3D Secure 2 authenticates transactions silently, requiring no input from the cardholder for low-risk payments. frictionless success

Using an amount different from the values listed above for the initial transaction ensures that subsequent recurring payments are always approved. This demonstrates the flexibility of the system in handling different transaction types.