Parameter Descriptions
Request Fields
Below is a list of the different request fields used when sending Host-Based Transactions.
Tagging Transactions for Reporting
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:
|
| Amount | The amount of money for which the transaction is being performed. Does not include the |
| Authorization Number | This field is used for Force Post transactions only. A Force Post transaction will allow you to deposit money which you already have authorization to charge. In order to do this, you will need to provide the original authorization number in this field. |
| Card Number | The card number for which the operation is being performed. |
| Customer Name | The name of the cardholder for reporting purposes. |
| Customer Email | The customers email address for reporting purposes. |
| Card Verification Value 2 Data | This 3 or 4 character field is used to ensure the physical presence of a card in an environment where the cardholder is not present at the time of the purchase. The CVV2 value appears as additional characters following the credit card number which is printed within the signature panel on the back of the card. (For some cards this number is on the front.) This field is used for VISA CVV2, MasterCard CVC and American Express Card Identifier Code (CID or 4DBC). |
| Description | Descriptive text that is added to the transaction. It is a searchable field in reporting. E.g.: U13 girls or Fall Tryouts |
| Expiry Date | The expiry date of the card on which the operation is being performed. |
| Invoice | 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. The intended way to use this field is to group transactions together such as Sale and Refund, or a declined Sale and later approved Sale. By keeping the invoice number the same, you will be able to view the entire transaction history of the registration. |
| Password | For added security, each |
| Platform Fee | The fee you are adding to the transaction, to be paid by the cardholder. Refer to Platform Billing. |
| Platform Charge | The fee you are subtracting from the approved transaction amount, to be paid by the merchant. Refer to Platform Billing. |
| 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 | A unique identifier for the transaction within the batch. Note: This is not the reference number which appears on the cardholder's statement. |
| Terminal ID | The Terminal ID is a unique 8 character long, alphanumeric code that is used to identify the source of the transaction. Each organization that is issued a merchant account with SportsPay will have a |
| Tokenized Card Data | Tokenized card data on file from a previous transaction. A |
| Transaction Type | The kind of transaction you are performing. See Transaction Types for values. Note: In order to fully understand the different transaction types, it is helpful to understand the transaction clearing process â see The Credit Card Charging Process. |
| Customer Pay User 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. Refer to UserFee for more details. |
Response Fields
Below are the response fields that your requests can receive depending on the request sent. At minimum, all transactions return a TEXT and an associated CODE field:
The CODE contains a 4-digit result code of â0000â for successful transactions and non-â0000â for transactions that were not successful. For a list of CODE values, refer to Errors & Troubleshooting.
Field | Name | Description |
|---|---|---|
| Authorization Number | For transactions which return authorization numbers (Sale, Pre-Authorization, Completion, Force Post, Auth Only), this is the authorization number.
The authorization number is also returned in the |
| Response Code | This is the 4-digit response code from the transaction. All transaction responses contain a |
| Date | The date of the transaction |
| Duration | The duration of the transaction on the server. This can be compared to the duration on the client to establish the communication overhead. |
| Hash | A one-way hash of the card data. This can be safely stored and used as a cardholder identifier without risking exposure of the actual card number. (It cannot be used for transactions). |
| Gateway Reference | A system-wide unique identifier assigned to each approved transaction. Unlike other reference numbers, the Gateway Reference is globally unique across all terminals, batches, and time. It can be used to query transactions throughout the entire system. |
| Text | This is the response text of the message and is included in the response for all transactions. The authorization number and amount are displayed here on an approval-type transaction. For errors and decline responses, this field contains the error message or decline message. |
| Time | The server clock for the transaction |
| Tokenized Card Data | Tokenized version of the card data. This value may be safely stored and used to perform future transactions. |
Authorized Amount in ResponseTEXTFieldOn approval-type transactions, the total amount will be shown in the text field. This will include the
PLATFEEor theUSERFEEif it was added to the transaction.
Updated about 21 hours ago
