Customized Checkout is the quickest way to start accepting payments with the lowest compliance burden. You send the customer to a SportsPay-hosted payment page themed to match your brand, then return them to your platform once the transaction is complete.

SportsPay hosts the payment page end-to-end. Your platform never touches card data, which keeps your PCI scope minimal and frees you from handling card entry, validation, and security in your own code.

Once integrated, Customized Checkout automatically picks up new gateway features without any changes on your side.

When to Use Customized Checkout

Use Customized Checkout when you want the fastest integration and the lowest compliance burden, and a full-page redirect to a branded payment page fits your customer flow.

If you need the payment form to appear inside your own checkout page (for example, in a modal or side panel without leaving your site), use Embedded Components instead. Both methods share the same three-message lifecycle (StartSession / GetResult / Ack) and the same brand theming — the difference is whether the customer is redirected away from your page or stays on it.

Branding

Customized Checkout is themed to match your brand. SportsPay customizes colors, gradients, button styles, border radii, and your logo so the payment page feels like a natural extension of your registration flow — not a hand-off to a third-party processor.

See Theming for how to submit your brand theme.

StartSession, GetResult, and Ack

Customized Checkout is handled through three gateway messages:

1. StartSession — Your server creates a payment session. The gateway returns a SECUREID and a URL.
2. Browser redirect — Your server redirects the customer's browser to the returned URL. The customer completes payment on the SportsPay-hosted page. When they're done, the gateway redirects them back to your SUCCESSURL or FAILUREURL.
3. GetResult — Your server calls the gateway with the SECUREID to retrieve the result of the transaction.
4. Ack — Your server confirms and finalizes the transaction. This can be combined with GetResult by passing ACK=Y, or sent as a separate call.

Each request includes the fields required for the gateway to validate the request and credit the correct merchant account. See Steps for Customized Checkout for the full request / response detail.

CustomerPay

No additional implementation is required to support CustomerPay with Customized Checkout.

• The gateway determines whether a merchant is enabled for CustomerPay based on the TERMID.
• The hosted page auto-calculates USERFEE and shows it to the customer.
• The final amount (including USERFEE) is returned in the GetResult response.

Payment Sequence

flowchart TD
    A[Customer completes registration] --> B[Registration platform sends StartSession]
    B --> C[Gateway returns SECUREID + Redirect URL]
    C --> D[Browser redirected to SportsPay hosted payment page]
    D --> E[Customer enters card details]
    E --> F[Payment processed by gateway]
    F --> G[Browser redirected to Success or Failure URL]
    G --> H[Registration platform sends GetResult]
    H --> I[Gateway returns payment result]
    I --> J{Ack required?}
    J -- Yes --> K[Registration platform sends Ack]
    K --> L[Gateway confirms and closes session]
    J -- No --> M[Session ends]
    L --> N[Registration platform continues user flow]
    M --> N