Key Data Structures

The following summarizes the key data structures used by the Paynetworx gateway.

NOTE

Card data and personally identifiable information as defined under either GDPR or CCPA, must be placed ONLY in fields specified for that purpose.

General data fields, such as 'MerchantData' fields, are provided for use in requests, and those are not to contain card data, bank account data, nor personally identifiable information.

The Transaction Class

The transaction class represents all supported transaction types.

Currently supported transaction types under the transaction class:

• AUTH
• BALANCE
• AUTH CAPTURE
• CAPTURE
• REFUND
• VERIFY
• VOID

The Query Class

The query class represents all supported queries into previous transactions.

Currently supported query types under the query class:

• QUERY LIST
• QUERY STATUS

Sample Transaction Flows using Key Data Structures

Authorization with immediate Capture

For an authorization with an immediate capture, use the following data structures.

1. AUTH CAPTURE

Authorization with separate Capture

For an authorization with a separate capture, use the following data structures.

1. AUTH
2. CAPTURE

Authorization Capture followed by Refund

For an authorization capture followed by a Refund, use the following data structures.

See the REFUND information for details on the timeframe for the Refund Window.

1. AUTH CAPTURE
2. REFUND

Authorization followed by Void

For an authorization capture followed by a Void, use the following data structures.

1. AUTH
2. Optional. Using Transaction ID from the Auth response, submit a QUERY STATUS
3. Using Transaction ID from the Auth response, submit a VOID

Authorization Capture with Technical Failure at initiating device

For an authorization capture where no response is received due to a technical failure at the initiating device, use the following data structures.

See the VOID information for details on the timeframe for the Void Window.

1. AUTH CAPTURE
2. QUERY LIST
3. Optional. Determined by transaction initiator. Using Transaction ID from Query List, submit a VOID