Parameter Descriptions
Request Fields
INV,REF,DESC,PROGRAM,PLAYER, andACCOUNTcan be used together to make transactions easily searchable and reconcilable in PaymentsHQ. See Transaction Tagging & Reporting Fields for guidance on how to use these fields effectively.
Field | Name | Description |
|---|---|---|
| Account(s) associated with the transaction | Optional parameter used to pass account-level allocation details for a transaction. When included, this data appears in the Deposit Report, allowing merchants to reconcile deposits by internal accounting categories such as tax allocations, bank accounts, or other financial buckets. Each entry includes:
Notes:
|
| Acknowledge | Call that tells the gateway to finalize the transaction |
| Action Type | The type of Web-Redirect request message being sent. |
| Amount | The amount of money for which the transaction is being performed. Any currency symbols must be removed, but the decimal point must be included. For example: â$4.00â becomes â4.00â
|
| Customer Email Address | The email address of the customer for reporting purposes. This is also a searchable field in our reporting. |
| Customer's Name | The name of the customer. This is also a searchable field in our reporting., |
| Description | Descriptive text that is added to the transaction. This is displayed on the payment page. It is a searchable field in reporting. E.g.: U13 girls or Fall Tryouts |
| Failure Return URL | The full URL where the customer will be redirected if the transaction is declined or encounters an error. This allows you to return the customer to a specific page (i.e. the registration form with an error message) so they can retry or choose another payment method. Must begin with "https://" |
| Invoice Number | The invoice number assigned to the transaction that is displayed in reporting as well as to the customer on the payment page. Acts as a âtagâ on the transaction and doesnât need to be unique. |
| Language | The language of the payment page with the option of English or French. Defaults to English. |
| Password | For added security, each |
| Platform Charge | The fee you are subtracting from the approved transaction amount, to be paid by the merchant. Refer to Platform Billing. |
| Platform Fee | The fee you are adding to the transaction, to be paid by the cardholder. Refer to Platform Billing. |
| Platform Billing | When used with StartSession, the gateway automatically applies this value as either a Platform Fee ( |
| Player(s) associated with the Transaction | Optional parameter used to pass player- or participant-level detail for a transaction. When included, this data appears in the Deposit Report, allowing merchants to reconcile deposits by individual player. Each entry includes:
Notes:
|
| Program(s) associated with the Transaction | Optional parameter used to pass program- or fee-level detail for a transaction. When included, this data appears in the Deposit Report, allowing merchants to reconcile deposits by program or fee type. Each entry includes:
Notes:
|
| Reference Number | The reference number you want to attach to the transaction. It must be unique within the batch. If omitted or blank, it will be assigned by the gateway. It is fully and partially searchable on reporting. |
| Request ID | The Request ID is generated by the registration platform and sent to the gateway. It is a message between your registration platform and the gateway and works to prevent duplicate sessions. It does not show up in any reporting. |
| Success Return URL | The full URL where the customer will be redirected after a successful transaction. This allows you to return the customer to a specific page (i.e. a registration confirmation page) after payment is completed. Must being with "https://" |
| Terminal ID | The Terminal ID is a unique 8 character long, alphanumeric code assigned by SportsPay that is used to identify the source of the transaction. Each organization that is issued a merchant account with SportsPay will have a |
| Transaction Type | The type of transaction message being sent. |
| Customer Pay Processing Fee | The Customer Pay processing fee to apply to the transaction. This is used for merchants who have opted into Customer Pay where the customer pays all processing fees at the time of checkout. |
Response Fields
Field | Name | Description |
|---|---|---|
| Card Expiration | Expiration date of the card. |
| Card Hash | Tokenized card hash used to identify the same card across transactions without exposing card data. |
| Card Mask | PCI-safe masked card number used to identify the card in reports and responses. |
| Card Type | The type of card used for the transaction in single letter format |
| Response Code | This is the 4-digit response code from the transaction
|
| Date | The date of the transaction |
| Duration | The amount of time the gateway required to process the request |
| Gateway Reference | A system-wide unique identifier assigned to each approved transaction and passed back in |
| Secure ID | The session identifier that is returned by |
| Response Text | Message indicating the result of the request: |
| Time | The server clock at the time of the transaction |
| Tokenized Card Data | Tokenized version of the card data. This value may be safely stored and used to perform future transactions |
| Redirect URL | A URL-Encoded string of the full URL for redirecting the customerâs browser. Note: Ampersands (&) in the URL will be encoded to %38 and must be decoded back to the ampersand (&) |
Updated about 21 hours ago
