Semi Integrated Transactions
An access API key issued to you by Xplor Pay.
Total transaction amount.
80.0Possible values: Transaction type to process. For example, SALE, AUTH, REFUND.
SALEPossible values: Card number or payment token.
4111111111111111Transaction identifier from a previous sale or authorization.
Card security code.
999Merchant-defined invoice number.
invoice123Description of the transaction.
Transaction descPossible values: Additional notes for the transaction.
Bad tipper .90 on 80.00 transactionPossible values: Cardholder verification method.
NON (None)Possible values: Card expiration date in MMyy format.
0932Clear-text Track 2 data.
textEncrypted track data; requires track-format.
textFormat of encrypted track data.
Tip amount applied to the transaction.
0.9Possible values: Authorization code for a forced sale obtained from an external processor.
AC789UPossible values: Merchant-defined purchase order number.
PO789Possible values: Indicates whether to send an email receipt to the customer.
falseThe customer's email address.
[email protected]Possible values: Merchant-defined customer identifier.
Customer 1234Possible values: Merchant-defined order identifier.
99988dPossible values: IP address where the request originated.
127.0.0.1Possible values: Indicates whether billing and shipping addresses match.
falseCreates a payment token during the transaction.
falseIndicates use of a legacy payment token.
falseDescription for the created token.
textPossible values: Card brand when creating a token.
VISAPossible values: EMV transaction data payload.
textKey serial number for EMV encryption.
textMethod used to capture EMV data.
EMV_DIPPossible values: Identifies the integrating application.
MySoftware_Version1.3Possible values: Version of the integrating application.
textEncrypted PIN data for PIN-based transactions.
textIndicates contactless usage (full EMV only).
falseIndicates contactless device usage (full EMV only).
falseSales tax amount applied to the transaction.
90.0Possible values: Sales tax classification.
LOCAL_SALES_TAXPossible values: Field used for duplicate transaction checks.
invoicePossible values: Service fee applied to the transaction.
2.9Possible values: Enables merchant-level duplicate validation for EMV.
trueIndicates whether the card is American Express.
falseIndicates whether the transaction is processed on an SP30 terminal.
falseValidates the card before token storage.
trueAllows partial approval when full amount is unavailable.
falseThe sales-tax-amount with respect to the total amount used for authorization and capture.
falseSuccessful Sale Transaction
Contains all details related to the authorized transaction.
Total value associated with the transaction.
Currency used for the transaction.
Unique transaction ID.
123456Invoice number associated with the transaction.
Test56Description of the transaction.
transaction descriptionComments associated with the transaction.
These are my commentsDate and time when the transaction was created.
8/10/2017 12:12:12:00 UTCIdentifies the transaction type.
SALEPossible values: Result of the transaction. For example, APPROVED.
APPROVEDPossible values: Card number used for the transaction.
Card Security Code used.
999Cardholder Verification Method used.
NONPossible values: Code indicating the transaction authorization.
AE12368Result code from Address Verification Service.
XPossible values: Description of the AVS result.
All digits match (9-digit Zip Code)Result code from CSC verification.
XPossible values: Description of the CSC result.
Service provider did not respondAmount of the adjusted tip.
1.0Street used in AVS check.
Example StreetZIP code used in AVS check.
85284Description of the token created.
Original amount before adjustments.
12.0Tip amount included in the transaction.
0.2Reference ID for the transaction.
568972Method used to enter payment data of the transaction. For example, Swipe/Manual.
EMV_DIPIndicates whether this is the first recurring transaction.
falseIdentifies the settlement batch ID.
000101Order id passed in with the transaction.
order99Purchase order number.
purcahseOrder88Customer id passed in with the transaction.
1234CustomerDisplayable message about transaction result.
Transaction ApprovedResult code associated with transaction result.
000Indicates if billing and shipping addresses are the same.
trueIndicates if the tip was adjusted.
falseExpiration date of the card.
1232IP address of the client initiating the transaction.
127.0.0.1Indicates if the transaction was voided.
falseIndicates if the transaction is pending.
falseIndicates if the authorization was voided.
falseIndicates if the transaction has been settled.
falseStatus of the transaction. For example, approved.
approvedRaw EMV data string.
0099daje93993903Serial number of the encryption key used.
0099daje93993903Method used to enter EMV data.
EMV_DIPPossible values: Type of software used for the transaction.
MySoftware_Version1.3First name of the customer.
JohnLast name of the customer.
DoeName of the payment plan used.
Plan 56Type of card used. For example, VISA.
VISAIndicates if contactless payment was used.
falseIndicates if a contactless device was used.
falseType of sales tax applied.
Amount of sales tax applied.
6.0Indicates if tax was added to the transaction amount.
falseResponse data from EMV processing.
Base64-encoded image of the signature.
Last four digits of the card number.
Indicates if a duplicate check was performed.
Service fee applied to the transaction
Base amount before taxes and fees.
Identifier for the merchant.
Identifier for the terminal used.
Indicates if a surcharge was applied.
Indicates if partial authorization was allowed.
falseIndicates if the transaction was partially approved.
falseElectronic Commerce Indicator for 3D Secure.
Result code from 3D Secure authentication.
Total amount including all charges.
Reference ID from the processing party.
Reference of the original transaction assigned by the processing party.
External reference ID for the transaction.
Reference for the funding transaction.
Identifier of the payment token.
Reference ID from the payment network for the transaction.
Indicates if a token should be created for the transaction.
Indicates whether the transaction is MOTO.
Identifier for the card issuer.
10Type of digital wallet used. For example, GOOGLE.
GOOGLESomething is wrong with your request
Unauthorized
Business Exception (decline, etc)
Internal server error
An access API key issued to you by Xplor Pay.
Total transaction amount.
80.0Possible values: Transaction type to process. For example, SALE, AUTH, REFUND.
SALEPossible values: Card number or payment token.
4111111111111111Transaction identifier from a previous sale or authorization.
Card security code.
999Merchant-defined invoice number.
invoice123Description of the transaction.
Transaction descPossible values: Additional notes for the transaction.
Bad tipper .90 on 80.00 transactionPossible values: Cardholder verification method.
NON (None)Possible values: Card expiration date in MMyy format.
0932Clear-text Track 2 data.
textEncrypted track data; requires track-format.
textFormat of encrypted track data.
Tip amount applied to the transaction.
0.9Possible values: Authorization code for a forced sale obtained from an external processor.
AC789UPossible values: Merchant-defined purchase order number.
PO789Possible values: Indicates whether to send an email receipt to the customer.
falseThe customer's email address.
[email protected]Possible values: Merchant-defined customer identifier.
Customer 1234Possible values: Merchant-defined order identifier.
99988dPossible values: IP address where the request originated.
127.0.0.1Possible values: Indicates whether billing and shipping addresses match.
falseCreates a payment token during the transaction.
falseIndicates use of a legacy payment token.
falseDescription for the created token.
textPossible values: Card brand when creating a token.
VISAPossible values: EMV transaction data payload.
textKey serial number for EMV encryption.
textMethod used to capture EMV data.
EMV_DIPPossible values: Identifies the integrating application.
MySoftware_Version1.3Possible values: Version of the integrating application.
textEncrypted PIN data for PIN-based transactions.
textIndicates contactless usage (full EMV only).
falseIndicates contactless device usage (full EMV only).
falseSales tax amount applied to the transaction.
90.0Possible values: Sales tax classification.
LOCAL_SALES_TAXPossible values: Field used for duplicate transaction checks.
invoicePossible values: Service fee applied to the transaction.
2.9Possible values: Enables merchant-level duplicate validation for EMV.
trueIndicates whether the card is American Express.
falseIndicates whether the transaction is processed on an SP30 terminal.
falseValidates the card before token storage.
trueAllows partial approval when full amount is unavailable.
falseThe sales-tax-amount with respect to the total amount used for authorization and capture.
falseSuccessful Sale Transaction
Contains all details related to the authorized transaction.
Total value associated with the transaction.
Currency used for the transaction.
Unique transaction ID.
123456Invoice number associated with the transaction.
Test56Description of the transaction.
transaction descriptionComments associated with the transaction.
These are my commentsDate and time when the transaction was created.
8/10/2017 12:12:12:00 UTCIdentifies the transaction type.
SALEPossible values: Result of the transaction. For example, APPROVED.
APPROVEDPossible values: Card number used for the transaction.
Card Security Code used.
999Cardholder Verification Method used.
NONPossible values: Code indicating the transaction authorization.
AE12368Result code from Address Verification Service.
XPossible values: Description of the AVS result.
All digits match (9-digit Zip Code)Result code from CSC verification.
XPossible values: Description of the CSC result.
Service provider did not respondAmount of the adjusted tip.
1.0Street used in AVS check.
Example StreetZIP code used in AVS check.
85284Description of the token created.
Original amount before adjustments.
12.0Tip amount included in the transaction.
0.2Reference ID for the transaction.
568972Method used to enter payment data of the transaction. For example, Swipe/Manual.
EMV_DIPIndicates whether this is the first recurring transaction.
falseIdentifies the settlement batch ID.
000101Order id passed in with the transaction.
order99Purchase order number.
purcahseOrder88Customer id passed in with the transaction.
1234CustomerDisplayable message about transaction result.
Transaction ApprovedResult code associated with transaction result.
000Indicates if billing and shipping addresses are the same.
trueIndicates if the tip was adjusted.
falseExpiration date of the card.
1232IP address of the client initiating the transaction.
127.0.0.1Indicates if the transaction was voided.
falseIndicates if the transaction is pending.
falseIndicates if the authorization was voided.
falseIndicates if the transaction has been settled.
falseStatus of the transaction. For example, approved.
approvedRaw EMV data string.
0099daje93993903Serial number of the encryption key used.
0099daje93993903Method used to enter EMV data.
EMV_DIPPossible values: Type of software used for the transaction.
MySoftware_Version1.3First name of the customer.
JohnLast name of the customer.
DoeName of the payment plan used.
Plan 56Type of card used. For example, VISA.
VISAIndicates if contactless payment was used.
falseIndicates if a contactless device was used.
falseType of sales tax applied.
Amount of sales tax applied.
6.0Indicates if tax was added to the transaction amount.
falseResponse data from EMV processing.
Base64-encoded image of the signature.
Last four digits of the card number.
Indicates if a duplicate check was performed.
Service fee applied to the transaction
Base amount before taxes and fees.
Identifier for the merchant.
Identifier for the terminal used.
Indicates if a surcharge was applied.
Indicates if partial authorization was allowed.
falseIndicates if the transaction was partially approved.
falseElectronic Commerce Indicator for 3D Secure.
Result code from 3D Secure authentication.
Total amount including all charges.
Reference ID from the processing party.
Reference of the original transaction assigned by the processing party.
External reference ID for the transaction.
Reference for the funding transaction.
Identifier of the payment token.
Reference ID from the payment network for the transaction.
Indicates if a token should be created for the transaction.
Indicates whether the transaction is MOTO.
Identifier for the card issuer.
10Type of digital wallet used. For example, GOOGLE.
GOOGLESomething is wrong with your request
Unauthorized
Business Exception (decline, etc)
Internal server error
An access API key issued to you by Xplor Pay.
Total transaction amount.
80.0Possible values: Transaction type to process. For example, SALE, AUTH, REFUND.
SALEPossible values: Card number or payment token.
4111111111111111Transaction identifier from a previous sale or authorization.
Card security code.
999Merchant-defined invoice number.
invoice123Description of the transaction.
Transaction descPossible values: Additional notes for the transaction.
Bad tipper .90 on 80.00 transactionPossible values: Cardholder verification method.
NON (None)Possible values: Card expiration date in MMyy format.
0932Clear-text Track 2 data.
textEncrypted track data; requires track-format.
textFormat of encrypted track data.
Tip amount applied to the transaction.
0.9Possible values: Authorization code for a forced sale obtained from an external processor.
AC789UPossible values: Merchant-defined purchase order number.
PO789Possible values: Indicates whether to send an email receipt to the customer.
falseThe customer's email address.
[email protected]Possible values: Merchant-defined customer identifier.
Customer 1234Possible values: Merchant-defined order identifier.
99988dPossible values: IP address where the request originated.
127.0.0.1Possible values: Indicates whether billing and shipping addresses match.
falseCreates a payment token during the transaction.
falseIndicates use of a legacy payment token.
falseDescription for the created token.
textPossible values: Card brand when creating a token.
VISAPossible values: EMV transaction data payload.
textKey serial number for EMV encryption.
textMethod used to capture EMV data.
EMV_DIPPossible values: Identifies the integrating application.
MySoftware_Version1.3Possible values: Version of the integrating application.
textEncrypted PIN data for PIN-based transactions.
textIndicates contactless usage (full EMV only).
falseIndicates contactless device usage (full EMV only).
falseSales tax amount applied to the transaction.
90.0Possible values: Sales tax classification.
LOCAL_SALES_TAXPossible values: Field used for duplicate transaction checks.
invoicePossible values: Service fee applied to the transaction.
2.9Possible values: Enables merchant-level duplicate validation for EMV.
trueIndicates whether the card is American Express.
falseIndicates whether the transaction is processed on an SP30 terminal.
falseValidates the card before token storage.
trueAllows partial approval when full amount is unavailable.
falseThe sales-tax-amount with respect to the total amount used for authorization and capture.
falseSuccessful Sale Transaction
Contains all details related to the authorized transaction.
Total value associated with the transaction.
Currency used for the transaction.
Unique transaction ID.
123456Invoice number associated with the transaction.
Test56Description of the transaction.
transaction descriptionComments associated with the transaction.
These are my commentsDate and time when the transaction was created.
8/10/2017 12:12:12:00 UTCIdentifies the transaction type.
SALEPossible values: Result of the transaction. For example, APPROVED.
APPROVEDPossible values: Card number used for the transaction.
Card Security Code used.
999Cardholder Verification Method used.
NONPossible values: Code indicating the transaction authorization.
AE12368Result code from Address Verification Service.
XPossible values: Description of the AVS result.
All digits match (9-digit Zip Code)Result code from CSC verification.
XPossible values: Description of the CSC result.
Service provider did not respondAmount of the adjusted tip.
1.0Street used in AVS check.
Example StreetZIP code used in AVS check.
85284Description of the token created.
Original amount before adjustments.
12.0Tip amount included in the transaction.
0.2Reference ID for the transaction.
568972Method used to enter payment data of the transaction. For example, Swipe/Manual.
EMV_DIPIndicates whether this is the first recurring transaction.
falseIdentifies the settlement batch ID.
000101Order id passed in with the transaction.
order99Purchase order number.
purcahseOrder88Customer id passed in with the transaction.
1234CustomerDisplayable message about transaction result.
Transaction ApprovedResult code associated with transaction result.
000Indicates if billing and shipping addresses are the same.
trueIndicates if the tip was adjusted.
falseExpiration date of the card.
1232IP address of the client initiating the transaction.
127.0.0.1Indicates if the transaction was voided.
falseIndicates if the transaction is pending.
falseIndicates if the authorization was voided.
falseIndicates if the transaction has been settled.
falseStatus of the transaction. For example, approved.
approvedRaw EMV data string.
0099daje93993903Serial number of the encryption key used.
0099daje93993903Method used to enter EMV data.
EMV_DIPPossible values: Type of software used for the transaction.
MySoftware_Version1.3First name of the customer.
JohnLast name of the customer.
DoeName of the payment plan used.
Plan 56Type of card used. For example, VISA.
VISAIndicates if contactless payment was used.
falseIndicates if a contactless device was used.
falseType of sales tax applied.
Amount of sales tax applied.
6.0Indicates if tax was added to the transaction amount.
falseResponse data from EMV processing.
Base64-encoded image of the signature.
Last four digits of the card number.
Indicates if a duplicate check was performed.
Service fee applied to the transaction
Base amount before taxes and fees.
Identifier for the merchant.
Identifier for the terminal used.
Indicates if a surcharge was applied.
Indicates if partial authorization was allowed.
falseIndicates if the transaction was partially approved.
falseElectronic Commerce Indicator for 3D Secure.
Result code from 3D Secure authentication.
Total amount including all charges.
Reference ID from the processing party.
Reference of the original transaction assigned by the processing party.
External reference ID for the transaction.
Reference for the funding transaction.
Identifier of the payment token.
Reference ID from the payment network for the transaction.
Indicates if a token should be created for the transaction.
Indicates whether the transaction is MOTO.
Identifier for the card issuer.
10Type of digital wallet used. For example, GOOGLE.
GOOGLESomething is wrong with your request
Unauthorized
Business Exception (decline etc)
Internal server error
An access API key issued to you by Xplor Pay.
Total transaction amount.
80.0Possible values: Transaction type to process. For example, SALE, AUTH, REFUND.
SALEPossible values: Card number or payment token.
4111111111111111Transaction identifier from a previous sale or authorization.
Card security code.
999Merchant-defined invoice number.
invoice123Description of the transaction.
Transaction descPossible values: Additional notes for the transaction.
Bad tipper .90 on 80.00 transactionPossible values: Cardholder verification method.
NON (None)Possible values: Card expiration date in MMyy format.
0932Clear-text Track 2 data.
textEncrypted track data; requires track-format.
textFormat of encrypted track data.
Tip amount applied to the transaction.
0.9Possible values: Authorization code for a forced sale obtained from an external processor.
AC789UPossible values: Merchant-defined purchase order number.
PO789Possible values: Indicates whether to send an email receipt to the customer.
falseThe customer's email address.
[email protected]Possible values: Merchant-defined customer identifier.
Customer 1234Possible values: Merchant-defined order identifier.
99988dPossible values: IP address where the request originated.
127.0.0.1Possible values: Indicates whether billing and shipping addresses match.
falseCreates a payment token during the transaction.
falseIndicates use of a legacy payment token.
falseDescription for the created token.
textPossible values: Card brand when creating a token.
VISAPossible values: EMV transaction data payload.
textKey serial number for EMV encryption.
textMethod used to capture EMV data.
EMV_DIPPossible values: Identifies the integrating application.
MySoftware_Version1.3Possible values: Version of the integrating application.
textEncrypted PIN data for PIN-based transactions.
textIndicates contactless usage (full EMV only).
falseIndicates contactless device usage (full EMV only).
falseSales tax amount applied to the transaction.
90.0Possible values: Sales tax classification.
LOCAL_SALES_TAXPossible values: Field used for duplicate transaction checks.
invoicePossible values: Service fee applied to the transaction.
2.9Possible values: Enables merchant-level duplicate validation for EMV.
trueIndicates whether the card is American Express.
falseIndicates whether the transaction is processed on an SP30 terminal.
falseValidates the card before token storage.
trueAllows partial approval when full amount is unavailable.
falseThe sales-tax-amount with respect to the total amount used for authorization and capture.
falseSuccessful Sale Transaction
Contains all details related to the authorized transaction.
Total value associated with the transaction.
Currency used for the transaction.
Unique transaction ID.
123456Invoice number associated with the transaction.
Test56Description of the transaction.
transaction descriptionComments associated with the transaction.
These are my commentsDate and time when the transaction was created.
8/10/2017 12:12:12:00 UTCIdentifies the transaction type.
SALEPossible values: Result of the transaction. For example, APPROVED.
APPROVEDPossible values: Card number used for the transaction.
Card Security Code used.
999Cardholder Verification Method used.
NONPossible values: Code indicating the transaction authorization.
AE12368Result code from Address Verification Service.
XPossible values: Description of the AVS result.
All digits match (9-digit Zip Code)Result code from CSC verification.
XPossible values: Description of the CSC result.
Service provider did not respondAmount of the adjusted tip.
1.0Street used in AVS check.
Example StreetZIP code used in AVS check.
85284Description of the token created.
Original amount before adjustments.
12.0Tip amount included in the transaction.
0.2Reference ID for the transaction.
568972Method used to enter payment data of the transaction. For example, Swipe/Manual.
EMV_DIPIndicates whether this is the first recurring transaction.
falseIdentifies the settlement batch ID.
000101Order id passed in with the transaction.
order99Purchase order number.
purcahseOrder88Customer id passed in with the transaction.
1234CustomerDisplayable message about transaction result.
Transaction ApprovedResult code associated with transaction result.
000Indicates if billing and shipping addresses are the same.
trueIndicates if the tip was adjusted.
falseExpiration date of the card.
1232IP address of the client initiating the transaction.
127.0.0.1Indicates if the transaction was voided.
falseIndicates if the transaction is pending.
falseIndicates if the authorization was voided.
falseIndicates if the transaction has been settled.
falseStatus of the transaction. For example, approved.
approvedRaw EMV data string.
0099daje93993903Serial number of the encryption key used.
0099daje93993903Method used to enter EMV data.
EMV_DIPPossible values: Type of software used for the transaction.
MySoftware_Version1.3First name of the customer.
JohnLast name of the customer.
DoeName of the payment plan used.
Plan 56Type of card used. For example, VISA.
VISAIndicates if contactless payment was used.
falseIndicates if a contactless device was used.
falseType of sales tax applied.
Amount of sales tax applied.
6.0Indicates if tax was added to the transaction amount.
falseResponse data from EMV processing.
Base64-encoded image of the signature.
Last four digits of the card number.
Indicates if a duplicate check was performed.
Service fee applied to the transaction
Base amount before taxes and fees.
Identifier for the merchant.
Identifier for the terminal used.
Indicates if a surcharge was applied.
Indicates if partial authorization was allowed.
falseIndicates if the transaction was partially approved.
falseElectronic Commerce Indicator for 3D Secure.
Result code from 3D Secure authentication.
Total amount including all charges.
Reference ID from the processing party.
Reference of the original transaction assigned by the processing party.
External reference ID for the transaction.
Reference for the funding transaction.
Identifier of the payment token.
Reference ID from the payment network for the transaction.
Indicates if a token should be created for the transaction.
Indicates whether the transaction is MOTO.
Identifier for the card issuer.
10Type of digital wallet used. For example, GOOGLE.
GOOGLESomething is wrong with your request
Unauthorized
Business Exception (decline, etc)
Internal server error
An access API key issued to you by Xplor Pay.
Total transaction amount.
80.0Possible values: Transaction type to process. For example, SALE, AUTH, REFUND.
SALEPossible values: Card number or payment token.
4111111111111111Transaction identifier from a previous sale or authorization.
Card security code.
999Merchant-defined invoice number.
invoice123Description of the transaction.
Transaction descPossible values: Additional notes for the transaction.
Bad tipper .90 on 80.00 transactionPossible values: Cardholder verification method.
NON (None)Possible values: Card expiration date in MMyy format.
0932Clear-text Track 2 data.
textEncrypted track data; requires track-format.
textFormat of encrypted track data.
Tip amount applied to the transaction.
0.9Possible values: Authorization code for a forced sale obtained from an external processor.
AC789UPossible values: Merchant-defined purchase order number.
PO789Possible values: Indicates whether to send an email receipt to the customer.
falseThe customer's email address.
[email protected]Possible values: Merchant-defined customer identifier.
Customer 1234Possible values: Merchant-defined order identifier.
99988dPossible values: IP address where the request originated.
127.0.0.1Possible values: Indicates whether billing and shipping addresses match.
falseCreates a payment token during the transaction.
falseIndicates use of a legacy payment token.
falseDescription for the created token.
textPossible values: Card brand when creating a token.
VISAPossible values: EMV transaction data payload.
textKey serial number for EMV encryption.
textMethod used to capture EMV data.
EMV_DIPPossible values: Identifies the integrating application.
MySoftware_Version1.3Possible values: Version of the integrating application.
textEncrypted PIN data for PIN-based transactions.
textIndicates contactless usage (full EMV only).
falseIndicates contactless device usage (full EMV only).
falseSales tax amount applied to the transaction.
90.0Possible values: Sales tax classification.
LOCAL_SALES_TAXPossible values: Field used for duplicate transaction checks.
invoicePossible values: Service fee applied to the transaction.
2.9Possible values: Enables merchant-level duplicate validation for EMV.
trueIndicates whether the card is American Express.
falseIndicates whether the transaction is processed on an SP30 terminal.
falseValidates the card before token storage.
trueAllows partial approval when full amount is unavailable.
falseThe sales-tax-amount with respect to the total amount used for authorization and capture.
falseSuccessful Sale Transaction
Contains all details related to the authorized transaction.
Total value associated with the transaction.
Currency used for the transaction.
Unique transaction ID.
123456Invoice number associated with the transaction.
Test56Description of the transaction.
transaction descriptionComments associated with the transaction.
These are my commentsDate and time when the transaction was created.
8/10/2017 12:12:12:00 UTCIdentifies the transaction type.
SALEPossible values: Result of the transaction. For example, APPROVED.
APPROVEDPossible values: Card number used for the transaction.
Card Security Code used.
999Cardholder Verification Method used.
NONPossible values: Code indicating the transaction authorization.
AE12368Result code from Address Verification Service.
XPossible values: Description of the AVS result.
All digits match (9-digit Zip Code)Result code from CSC verification.
XPossible values: Description of the CSC result.
Service provider did not respondAmount of the adjusted tip.
1.0Street used in AVS check.
Example StreetZIP code used in AVS check.
85284Description of the token created.
Original amount before adjustments.
12.0Tip amount included in the transaction.
0.2Reference ID for the transaction.
568972Method used to enter payment data of the transaction. For example, Swipe/Manual.
EMV_DIPIndicates whether this is the first recurring transaction.
falseIdentifies the settlement batch ID.
000101Order id passed in with the transaction.
order99Purchase order number.
purcahseOrder88Customer id passed in with the transaction.
1234CustomerDisplayable message about transaction result.
Transaction ApprovedResult code associated with transaction result.
000Indicates if billing and shipping addresses are the same.
trueIndicates if the tip was adjusted.
falseExpiration date of the card.
1232IP address of the client initiating the transaction.
127.0.0.1Indicates if the transaction was voided.
falseIndicates if the transaction is pending.
falseIndicates if the authorization was voided.
falseIndicates if the transaction has been settled.
falseStatus of the transaction. For example, approved.
approvedRaw EMV data string.
0099daje93993903Serial number of the encryption key used.
0099daje93993903Method used to enter EMV data.
EMV_DIPPossible values: Type of software used for the transaction.
MySoftware_Version1.3First name of the customer.
JohnLast name of the customer.
DoeName of the payment plan used.
Plan 56Type of card used. For example, VISA.
VISAIndicates if contactless payment was used.
falseIndicates if a contactless device was used.
falseType of sales tax applied.
Amount of sales tax applied.
6.0Indicates if tax was added to the transaction amount.
falseResponse data from EMV processing.
Base64-encoded image of the signature.
Last four digits of the card number.
Indicates if a duplicate check was performed.
Service fee applied to the transaction
Base amount before taxes and fees.
Identifier for the merchant.
Identifier for the terminal used.
Indicates if a surcharge was applied.
Indicates if partial authorization was allowed.
falseIndicates if the transaction was partially approved.
falseElectronic Commerce Indicator for 3D Secure.
Result code from 3D Secure authentication.
Total amount including all charges.
Reference ID from the processing party.
Reference of the original transaction assigned by the processing party.
External reference ID for the transaction.
Reference for the funding transaction.
Identifier of the payment token.
Reference ID from the payment network for the transaction.
Indicates if a token should be created for the transaction.
Indicates whether the transaction is MOTO.
Identifier for the card issuer.
10Type of digital wallet used. For example, GOOGLE.
GOOGLESomething is wrong with your request
Unauthorized
Business Exception (decline, etc)
Internal server error
An access API key issued to you by Xplor Pay.
Total transaction amount.
80.0Possible values: Transaction type to process. For example, SALE, AUTH, REFUND.
SALEPossible values: Card number or payment token.
4111111111111111Transaction identifier from a previous sale or authorization.
Card security code.
999Merchant-defined invoice number.
invoice123Description of the transaction.
Transaction descPossible values: Additional notes for the transaction.
Bad tipper .90 on 80.00 transactionPossible values: Cardholder verification method.
NON (None)Possible values: Card expiration date in MMyy format.
0932Clear-text Track 2 data.
textEncrypted track data; requires track-format.
textFormat of encrypted track data.
Tip amount applied to the transaction.
0.9Possible values: Authorization code for a forced sale obtained from an external processor.
AC789UPossible values: Merchant-defined purchase order number.
PO789Possible values: Indicates whether to send an email receipt to the customer.
falseThe customer's email address.
[email protected]Possible values: Merchant-defined customer identifier.
Customer 1234Possible values: Merchant-defined order identifier.
99988dPossible values: IP address where the request originated.
127.0.0.1Possible values: Indicates whether billing and shipping addresses match.
falseCreates a payment token during the transaction.
falseIndicates use of a legacy payment token.
falseDescription for the created token.
textPossible values: Card brand when creating a token.
VISAPossible values: EMV transaction data payload.
textKey serial number for EMV encryption.
textMethod used to capture EMV data.
EMV_DIPPossible values: Identifies the integrating application.
MySoftware_Version1.3Possible values: Version of the integrating application.
textEncrypted PIN data for PIN-based transactions.
textIndicates contactless usage (full EMV only).
falseIndicates contactless device usage (full EMV only).
falseSales tax amount applied to the transaction.
90.0Possible values: Sales tax classification.
LOCAL_SALES_TAXPossible values: Field used for duplicate transaction checks.
invoicePossible values: Service fee applied to the transaction.
2.9Possible values: Enables merchant-level duplicate validation for EMV.
trueIndicates whether the card is American Express.
falseIndicates whether the transaction is processed on an SP30 terminal.
falseValidates the card before token storage.
trueAllows partial approval when full amount is unavailable.
falseThe sales-tax-amount with respect to the total amount used for authorization and capture.
falseSuccessful Sale Transaction
Contains all details related to the authorized transaction.
Total value associated with the transaction.
Currency used for the transaction.
Unique transaction ID.
123456Invoice number associated with the transaction.
Test56Description of the transaction.
transaction descriptionComments associated with the transaction.
These are my commentsDate and time when the transaction was created.
8/10/2017 12:12:12:00 UTCIdentifies the transaction type.
SALEPossible values: Result of the transaction. For example, APPROVED.
APPROVEDPossible values: Card number used for the transaction.
Card Security Code used.
999Cardholder Verification Method used.
NONPossible values: Code indicating the transaction authorization.
AE12368Result code from Address Verification Service.
XPossible values: Description of the AVS result.
All digits match (9-digit Zip Code)Result code from CSC verification.
XPossible values: Description of the CSC result.
Service provider did not respondAmount of the adjusted tip.
1.0Street used in AVS check.
Example StreetZIP code used in AVS check.
85284Description of the token created.
Original amount before adjustments.
12.0Tip amount included in the transaction.
0.2Reference ID for the transaction.
568972Method used to enter payment data of the transaction. For example, Swipe/Manual.
EMV_DIPIndicates whether this is the first recurring transaction.
falseIdentifies the settlement batch ID.
000101Order id passed in with the transaction.
order99Purchase order number.
purcahseOrder88Customer id passed in with the transaction.
1234CustomerDisplayable message about transaction result.
Transaction ApprovedResult code associated with transaction result.
000Indicates if billing and shipping addresses are the same.
trueIndicates if the tip was adjusted.
falseExpiration date of the card.
1232IP address of the client initiating the transaction.
127.0.0.1Indicates if the transaction was voided.
falseIndicates if the transaction is pending.
falseIndicates if the authorization was voided.
falseIndicates if the transaction has been settled.
falseStatus of the transaction. For example, approved.
approvedRaw EMV data string.
0099daje93993903Serial number of the encryption key used.
0099daje93993903Method used to enter EMV data.
EMV_DIPPossible values: Type of software used for the transaction.
MySoftware_Version1.3First name of the customer.
JohnLast name of the customer.
DoeName of the payment plan used.
Plan 56Type of card used. For example, VISA.
VISAIndicates if contactless payment was used.
falseIndicates if a contactless device was used.
falseType of sales tax applied.
Amount of sales tax applied.
6.0Indicates if tax was added to the transaction amount.
falseResponse data from EMV processing.
Base64-encoded image of the signature.
Last four digits of the card number.
Indicates if a duplicate check was performed.
Service fee applied to the transaction
Base amount before taxes and fees.
Identifier for the merchant.
Identifier for the terminal used.
Indicates if a surcharge was applied.
Indicates if partial authorization was allowed.
falseIndicates if the transaction was partially approved.
falseElectronic Commerce Indicator for 3D Secure.
Result code from 3D Secure authentication.
Total amount including all charges.
Reference ID from the processing party.
Reference of the original transaction assigned by the processing party.
External reference ID for the transaction.
Reference for the funding transaction.
Identifier of the payment token.
Reference ID from the payment network for the transaction.
Indicates if a token should be created for the transaction.
Indicates whether the transaction is MOTO.
Identifier for the card issuer.
10Type of digital wallet used. For example, GOOGLE.
GOOGLESomething is wrong with your request
Unauthorized
Business Exception (decline, etc)
Internal server error
Last updated
Was this helpful?

