Web-Redirect payments use the InterPay™ gateway, your registration platform, and the customer’s browser to process payments securely.

SportsPay hosts the payment page where the customer enters their card details. Your platform never handles card data, reducing PCI scope and simplifying compliance.

Once integrated, Web-Redirect automatically supports new gateway features without requiring changes on your side.

CustomerPay

No additional implementation is required to support CustomerPay with Web-Redirect.

• The gateway determines whether a merchant is enabled for CustomerPay based on the TERMID
• The hosted payment page calculates and applies the USERFEE automatically
• The final USERFEE amount is returned in the GetResult response after payment completion

StartSession, GetResult, and Ack

Web-Redirect processing is handled through three gateway messages:

1. StartSession – Creates a payment session and returns a redirect URL
2. GetResult– Retrieves the result of the completed payment
3. Ack– Confirms and finalizes the transaction (optional)

Each request includes required fields that allow the gateway to validate the request and credit the correct merchant account. Responses include a consistent set of fields regardless of message type.

Payment Sequence

flowchart TD
    A[Customer completes registration] --> B[Registration platform sends StartSession]
    B --> C[Gateway returns SECUREID + Redirect URL]
    C --> D[Browser redirects 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[Registration platform continues user flow]

1. The customer completes registration and proceeds to payment
2. Your server sends a StartSession request to the InterPay™ gateway
3. The gateway responds with a SECUREID and a hosted payment URL
4. The customer’s browser is redirected to the hosted payment page
5. The customer enters their card details and submits payment
6. The gateway redirects the browser back to the configured Success or Failure URL
7. Your server sends a GetResult request using the returned SECUREID
8. The gateway returns the payment result
9. (Optional) Your server sends an Ack request to confirm processing
10. (Optional) The gateway confirms and closes the session
11. Your application continues the user flow (confirmation, receipt, next steps)