SportsPay provides payment processing for amateur sports registration platforms. Our APIs allow you to accept credit card payments, manage fees, and handle complex payment flows such as splits, transfers, and scheduled payments.

This documentation is intended for developers building or maintaining a SportsPay integration. You'll find API references, required fields, and implementation guidance needed to get up and running quickly.

New here? Head to the Quick Start guide to get test credentials and run your first transaction in minutes.

Integration Methods

SportsPay supports three integration methods. All three keep card data off your servers — the difference is where the customer enters their card details and how much control you have over the checkout experience.

	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 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 — colours, gradients, and logo	Themed to match your brand, plus control over which visual components appear	You build the UI entirely
Advanced Features	Auto-handled	Auto-handled	You implement
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

Customized Checkout

The customer is sent to a SportsPay-hosted payment page themed to match your brand, then redirected back to your platform. The redirect is flexible — open it in a new tab, the current window, or inside a modal/dialog on your platform so the customer never feels like they left your site. SportsPay works with you to customize colors, gradients, and logo so the checkout feels like a natural extension of your registration flow. Card data is never handled by your system.

Learn more

Embedded Components

The SportsPay payment fragment is rendered inside your own checkout flow — in a modal, side panel, or inline step — rather than redirecting the customer away. Mount it into a <div> on your page using the SportsPay JavaScript library, or embed the URL returned from StartSession directly into an <iframe>. Either way, the fragment runs inside an iframe that keeps card data off your servers. The fragment seamlessly handles advanced functionality like schedules, CustomerPay, Platform Fees, wallets, and retries, plus future enhancements, with no additional integration work on your side. The same brand theming from Customized Checkout applies, and you control which visual components appear using the EMBED= flag.

Learn more

Direct with Embedded Tokenization

Your platform submits transactions directly to the InterPay™ gateway. Card data is securely tokenized in the browser using InterPay JavaScript — a one-time token is generated and sent to the gateway, and a permanent token is returned for future use with the same card. Your server never handles raw card data. You are responsible for building and styling the checkout UI, and for implementing advanced functionality — schedules, CustomerPay, Platform Fees, and wallets — on your side. If you'd rather have those handled automatically, use Customized Checkout or Embedded Components.

Learn more

Core Features

SportsPay offers several features you can layer on top of any of the three integration methods:

Platform Billing

Platform Fees (PLATFEE) and Platform Charges (PLATCHRG) allow you to collect your own fees as part of a transaction.

Fees are tied to the transaction
Funds are deposited directly into your bank account
SportsPay does not take a share of these fees

CustomerPay

A pricing model where the cardholder's total includes a calculated USERFEE.

USERFEE is calculated by SportsPay based on the merchant's pricing
Returned in the transaction response
Returns 0 if the merchant is not enabled for CustomerPay

Transfers: Inter-Merchant & Splits

Distribute funds across multiple merchants in one transaction, or as a standalone transfer.

Common use cases include:

Governing body fees
Revenue sharing
Multi-party registrations

Payment Schedules

Run multiple future payments against a saved card on a fixed timeline:

Create, update, and track schedules
Card data can be added via Customized Checkout, Embedded Components, or Direct with Embedded Tokenization
Payments are automatically processed on scheduled dates
Status updates are sent back to your platform

Reporting & Querying

Reporting APIs allow access to transaction and deposit data.

Available calls include:

Transaction Query – search transactions
Deposit Query – view deposited transactions
Mirror Reporting – opens PaymentsHQ within your platform

Terminals

Offer your merchants in-person card payments on a physical terminal via an asynchronous API.

StartSession dispatches the request to the terminal
Final transaction result is delivered via webhook callback
Supports both sale and refund transactions
Merchant and customer receipts are returned with the result

For guidance on tagging transactions for effective reporting, see Transaction Tagging & Reporting Fields.