Skip to main content

Checkout Page

This is the page the customer sees after the redirect. It contains the fields required by the chosen payment method.

info

If you sent email or billing_address in the request, those fields are not shown on the Checkout Page (you already have them). If you did not send them and the method needs them, they are shown for the customer to fill in.

Fields and validations​

FieldTypeLimitError shown
Card numberIntegralLuhn, 14–19 digitsInvalid card number
Expiry dateDatemm/yy, later than todayThe expiration date of card is expired and not valid
Security codeIntegralup to 4 charactersInvalid security code
Name on cardStringmax 32, at least 2 wordsMust contain first name and last name
CountryList2-letter codeCountry is required / Please enter a valid Country
State/RegionString/List*—List only for USA, Canada, Australia, Japan, India
CityStringmax 32City is required
AddressStringmax 32Address line is required
Postal codeStringmax 32Zip code is required
PhoneStringmax 32Phone number is required

Pre-routing​

To simplify the payment method choice, you can configure pre-routing rules in the admin panel (Custom Routing module), which determine which methods are valid for each payment — preventing the customer from choosing a method that is not available in their region.

warning

If the request includes the methods array, pre-routing rules are ignored.

Card tokenization​

For returning customers, you can save the card details:

  1. Send req_token: true in the authentication request.
  2. You receive a card_token in the callback.
  3. On the next request, send that card_token — the customer will see the anonymized details in the form.

Web information​

Checkout collects information about the browser the customer is using. While the customer is on the Checkout Page, the service gathers data about the operating system, the browser and the browser language. That information is sent to the acquirer in some cases, depending on what the payment method requires.

Redirect types​

TypeDescription
POST redirectWith parameters (form POST) or without parameters
GET redirectParameters in the query string
Memory StorageSee below

Enabled under Configuration → Protocol Mapping → Edit Protocol Mapping → "Use memory storage to save redirect parameters".

With this enabled:

  1. The redirect data (parameters, payload, metadata) is stored on the provider side.
  2. A simple redirect URL is returned to the merchant.
  3. The merchant redirects the payer to that URL.
  4. A wrapper endpoint retrieves the stored data, builds the form POST and auto-submits it to the merchant.
Link example
{
"redirect_url": "https://checkout.rafinita.com/wrapper/026f9cd4-ec2a-11f0-9a2d-9efd82971246/7e9dc650db39212ea2fda44201207ea3",
"redirect_method": "GET"
}
Example POST redirect
{
"redirect_params": {
"body": "K1o1bGZNMXZGS2RTMlNIYmgzWlExV1hiN3FkcXAyMmlZSDFPZkFsR3czZnRZa1E5b2xYT1ZsZWJncld6YUJJTFJWREdaUDlxQ3QvVWEyY2JBTU9wOWZpd0hXdVdoQXRiVFlrZ3RaOVNZZDZNL2JXTUdyV0NrdDlBaUNQZE5NaXZoTWNkcTlxVURSSkxaTWNEWXJ3aEtHWVdpODNWQzVRWlZWdVpFKzY5aWJjPTo6WjF6NDNkV0R0d1RYYnNneXhWZGEydz09"
},
"redirect_method": "POST"
}

Benefits:

  • Minimal integration (just a GET redirect, no HTML forms to build)
  • Better security (sensitive data does not travel in query params)
  • No risk of exceeding URL length limits (important for large 3DS payloads)
  • Fewer integration errors (encoding, missing parameters, broken auto-submit)
warning

Without Memory Storage, the merchant is responsible for preserving all parameters, rendering the form correctly, the auto-submit, and avoiding data loss or encoding issues.

Custom payment form​

If you prefer your own payment form, specify a unique identifier in the authentication request:

{ "form_id": "xxxxx-xxxxx-xxxxx" }

More information in SDK Checkout.

Page customization​

From the admin panel (Configuration → Branding, authorized users only):

  1. Choose the page template
  2. Configure: login icon, header color, background color, button colors
  3. Save