Click to Pay

Description

Click to Pay allows customers to pay with cards enrolled in the Secure Remote Commerce (SRC) network using their email address or mobile phone number.

With our integration, Click to Pay is available on the Hosted Payment Page only. No Click to Pay SDK or SRC integration is required on the merchant side — create a checkout session via the Checkout API and redirect the customer to the Hosted Payment Page.

info

Click to Pay is not available through POST /rest/payment (Payment Page Redirect) or a direct Payment API integration. Use the Checkout API to create a checkout session and redirect the customer to /rest/checkouts/{checkout_id}.

Availability

• Online (e-commerce) transactions on the Hosted Payment Page
• Available when Click to Pay is enabled for your merchant account (contact your onboarding manager)
• Not available in embedded iframe checkout contexts

Supported card networks depend on your account configuration (typically Mastercard and Visa; Amex and Discover may be available depending on the acquirer).

Transaction Types

The following transaction types are currently available:

• Payment (via Hosted Payment Page)
• Refund (Full and partial refund)

Integration Types

The following integration type is currently available:

• Checkout API — Hosted Payment Page

Payment Flow

Merchant Onboarding

Before accepting Click to Pay payments:

1. Contact your onboarding manager — Request activation of Click to Pay for your merchant account and provide the business details they ask for (e.g. business name, website URL, merchant category).
2. Integrate the Checkout API — Create checkout sessions and redirect customers to the Hosted Payment Page.
3. Handle postbacks — Process postback notifications and update order status in your system.

API Implementation

Create a checkout session using the Checkout API with the same parameters as any other hosted checkout. Click to Pay appears on the Hosted Payment Page automatically when it is enabled for your merchant account — no additional request fields are required.

Redirect the customer to action_data.url from the Checkout API response. The customer completes Click to Pay on the Hosted Payment Page and is then redirected to your success_url or error_url.

Postbacks

For the full list of payment postback fields, see the Payment API. For refund postbacks, see the Refund API. For retry policy and signature verification, see Postbacks.