Checkout settings

Open Settings > Checkout in the Tapaya Platform with an organization administrator account. Configure these settings before you integrate hosted Checkout.

Checkout settings apply to the merchant whose registration number matches your organization. If the page shows No matching merchant or Multiple matching merchants, check the registration numbers in Organization settings and Merchants. Checkout currently requires exactly one matching merchant. Support for multiple merchants per organization is planned for a future release.

Enable Checkout

Confirm with Tapaya that your merchant is configured for online payments. Turn on Enable Checkout to reveal the settings, configure the fields below, then select Save changes. Enabling Checkout does not complete merchant onboarding or provision payment credentials.

Turning off an already enabled Checkout saves immediately. Other unsaved field changes are not applied by that action.

Choose payment methods

Under Payment methods, choose whether to offer Apple Pay and Google Pay. Card payments are always enabled while Checkout is on. Select Save changes to apply wallet changes.

Wallet availability also depends on the customer's device, browser, and merchant configuration. Enabling a wallet does not guarantee that its button appears on every device. Live Google Pay requires a configured Google Pay merchant ID.

Configure return destinations

Under Redirect URLs, enter the Default success URL and Default cancel URL. Checkout uses these destinations to return customers to your shop after payment or when they choose to leave Checkout.

For example, a shop might use:

• Success URL: https://shop.example/checkout/return.
• Cancel URL: https://shop.example/checkout/cancel.
• Allowed redirect origin: https://shop.example.

Add each return destination's origin to Allowed redirect origins. Separate multiple origins with commas. An origin contains a scheme, host, and optional port. Do not include a path, query, or fragment. Matching uses the exact origin, including the effective port. Wildcards and hostname suffixes do not match.

Use HTTPS for deployed shops. Both default return URLs must match an allowed origin before you save with Checkout enabled. Select Save changes to apply the redirect settings.

If an order needs a different return path, supply successUrl or cancelUrl when creating its session. These per-session overrides must still match an origin configured in the Platform.

A visit to either return URL does not prove the payment outcome. Retrieve the session from your server before marking an order paid.

Set Checkout branding

Under Checkout appearance, set Checkout color to a six-digit hexadecimal color, such as #1380A5. Leave it empty or select Reset to use the organization color. Select Save changes to apply the color.

For Checkout logo, upload a PNG or WebP image no larger than 5 MB. Logo uploads and removals save immediately. Remove the Checkout logo override to use the organization logo again.

Use Checkout preview to review the branding and selected payment methods in desktop and mobile layouts.