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.

Integration Methods

SportsPay supports two different integration methods:

Direct Payments (with Embedded Tokenization)
Redirect Payments

Direct Payments with Embedded Tokenization

Direct Payments allow your platform to submit a transaction 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.

Learn more

Redirect Payments

Redirect Payments send the customer to SportsPay’s hosted payment page to complete the transaction, then redirect them back to your platform.

This option requires the least PCI scope, as card data is never handled by your system.

Learn more

Core Features

SportsPay includes functionality designed for amateur sports organizations and registration platforms.

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

Works with:

Direct Payments
Redirect Payments
CustomerPay (USERFEE)

CustomerPay

CustomerPay allows transaction fees to be passed to the cardholder at checkout using the USERFEE field.

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

Works with:

Direct Payments
Redirect Payments

Transfers: Inter-Merchant & Splits

Transfers allow funds to be distributed across multiple merchants in a single transaction.

Common use cases include:

Governing body fees
Revenue sharing
Multi-party registrations

Payment Schedules

Payment Schedules allow transactions to be split into multiple future payments.

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

Partner Charges

Partner Charges allow you to add charges to a merchant’s monthly statement.

Collected by SportsPay
Paid out as part of your revenue share
Currently managed through PaymentsHQ (API support planned)

Reporting & Querying

Reporting APIs allow access to transaction and deposit data.

Available calls include:

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

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