Quick Start
This guide will get you from zero to your first test transaction as quickly as possible
Get Your Test Credentials
SportsPay provides a sandbox environment for validating your integration before going live. Test transactions do not reach the card networks.
To request test credentials, email [email protected]
Choose an Integration Method
SportsPay supports three ways to accept payments. Choose the one that fits your platform:
| Customized Checkout | Embedded Components | Direct with Embedded Tokenization | |
|---|---|---|---|
| How it works | Customer is redirected to a SportsPay-hosted payment page (full-page or modal), then returned to your platform | SportsPay payment fragment is rendered inside your checkout via the JavaScript library or an iframe embed | Your platform submits transactions directly to the gateway using a secure browser-generated token |
| Card data handled by you? | No — entered directly on SportsPay's hosted page | No — entered in the SportsPay payment fragment | No — tokenized in the browser via InterPay JavaScript |
| Branding | Themed to match your brand — colors, gradients, and logo | Themed to match your brand, plus control over which visual components appear | You build the UI entirely |
| PCI scope | Card data is kept off your servers | Card data is kept off your servers | Card data is kept off your servers |
| Best for | Fastest integration with lowest compliance burden | In-page checkout experience without handling card data | Full control over the checkout UI |
→ Read the Customized Checkout overview
Brand Your Checkout
If you're using Customized Checkout or Embedded Components, SportsPay themes the hosted payment page to match your brand — colors, gradients, button styles, border radii, and your logo. Theming applies automatically to both hosted methods.
See Theming for how to submit your brand theme.
Note: If you're using Direct with Embedded Tokenization, you are responsible for building and styling the checkout UI yourself. The theming system does not apply.
Connect to the Test Gateway
Use your test credentials with one of the following gateway URLs:
Recommended (matches live behaviour):
Pre-production (early feature testing only — may change without notice):
Run a Test Transaction
Use the following test card numbers to simulate payments. Any future expiry date and any CVV value will work.
| Card Type | Card Number |
|---|---|
| Visa | 4000000000000002 |
| Mastercard | 5454545454545454 |
| American Express | 378282246310005 |
| Discover | 6011000000000004 |
To simulate a decline, use an amount ending in 1 (e.g. 20.01) or set the card expiry month to 04.
Validate in PaymentsHQ
Once you've run a test transaction, log in to PaymentsHQ to confirm the result:
- Partner login — view the gateway log and all transactions across merchants
- Test merchant login — validate the merchant experience and check fields like
INVfor transaction grouping
Go Live
When you're ready to move to production, see the Production guide for steps to switch over your credentials and gateway URLs.
What's Next?
Depending on your integration method, continue with:
- Customized Checkout — Steps for Customized Checkout
- Embedded Components — Steps for Embedded Components
- Direct with Embedded Tokenization — Transaction Types
- Technical Specifications
Need help? Email [email protected]
Updated about 23 hours ago