Includes order IDs, invoice numbers, and custom merchant-defined fields.

Transaction Details - Ancillary Data

Variable	Requirement	Type	Possible Values / Example	Description	Notes
`pt_order_classifier`	Optional	string	invoice123, userID456	Alphanumeric value used to track the payment with an order.	Typically used for invoice numbers, customer IDs, or external references.
`pt_order_id`	Optional	string	123456789	Unique numeric identifier for the transaction.	If not provided, a system-generated ID based on timestamp will be used. Required for voids, refunds, and returns.
`pb_remote_session`	Optional	string	session_abc123	Session identifier associated with the transaction.	Used for session tracking and reconciliation.
`pt_account_code_1`	Optional	string	max 20 chars	Custom account code stored with transaction.	Can be used for filtering or administrative reporting.
`pt_account_code_2`	Optional	string	max 20 chars	Additional account code field.	Same usage as `pt_account_code_1`.
`pt_account_code_3`	Optional	string	max 20 chars	Additional account code field.	Same usage as `pt_account_code_1`.
`pt_custom_name_#`	Optional	string	custom_field_1	Name of a merchant-defined custom field.	Must be paired with `pt_custom_value_#`. Fields must be sequential starting at 1. ¹
`pt_custom_value_#`	Optional	string	custom_value_1	Value for a merchant-defined custom field.	Must match corresponding `pt_custom_name_#`. ¹

Custom fields must be submitted as name/value pairs (e.g., pt_custom_name_1 + pt_custom_value_1). Fields must be sequential starting from 1 with no gaps (e.g., 1, 2, 3…). Missing sequence numbers may result in fields being ignored. ↩︎ ↩︎