Transaction Details - Ancillary Data
Variable | Requirement | Type | Possible Values | Description |
pt_order_classifier | Optional | string | Alphanumeric value generated by you - can be an invoice or customer username/ID to use to track the payment with the order. | |
pt_order_id | Optional | string | numeric values only | Unique numeric identifier for transaction. Must be a unique number. If not submitted one will be generated using a date/time string. This number is required to perform any future activity for an order, including but not limited to voids and returns. |
pb_remote_session | Optional | string | Used to pass a session ID with the transaction. | |
pt_account_code_1 | Optional | string | up to 20 alphanumeric characters | Include this field with your orders/transactions to store it’s value to our database with other transaction data. You can later use this field to filter/select only those orders which match the value passed when using many of the administrative functions. |
pt_account_code_2 | Optional | string | up to 20 alphanumeric characters | additional account code field, see pt_account_code_1 for details |
pt_account_code_3 | Optional | string | up to 20 alphanumeric characters | additional account code field, see pt_account_code_1 for details |
pt_custom_name_# | Optional | string | Used to send name of your own custom field. See Note 1 | |
pt_custom_value_# | Optional | string | Used to send value of your own custom field. See Note 1 |
Notes:
- Custom Fields are sent in pairs of name/value (i.e. pt_custom_name_1 and pt_custom_value_1). Custom Fields should be sent in order starting from 1.