Transaction Types Available

Transaction Types Available

E-xact’s services can be configured and set up for many transaction types. The transaction types available are listed below:

Standard Transactions

Transaction Type Description Transaction Code Compatible Services
Purchase Sends through sale and request for funds to be charged to cardholder’s credit card. 00 API, Recurring, Payment Pages, POS
Pre-Authorization Sends through a request for funds to be “reserved” on the cardholder’s credit card. A standard pre-authorization is reserved for 2-5 days. Reservation times are determined by cardholder’s bank. 01 API, Recurring, Payment Pages, POS
Pre-Authorization Completion Completes an existing pre-authorization by referencing an authorization number. 02 API, POS
Refund Sends through a request for funds to be returned to the cardholder. 04 API, Recurring, POS
Void Sends through a void to prevent the settlement of the funds. Voids must be processed on the same day as the authorization. 13 API, POS
Forced Post Completes a transaction that was not authorized on E-xact’s system i.e. Voice Authorizations or other sources. The Authorization number provided by the Card Company must be contained in the Forced Post Transaction. You will need permissions and procedural outlines from E-xact prior to use. 03 API, Recurring, POS

Tagged Transactions

Tagged transactions enable a transaction to be processed without having to send a credit card number. Tags and how they function are outlined below:

Transaction Type Description Transaction Code Compatible Services
Recurring Seed Sends through a request to allow a merchant to pre-authorize a credit card. The data produced by the Pre-Authorization creates a seed. The seed may then be used to send many Tagged Purchase transactions or one Tagged Completion. 40 API, Payment Pages
Recurring Seed Purchase Applies a purchase against the credit card provided. Funds for the specified amount are settled to the merchant’s account at the end of the day. Tagged Refunds equal to the amount of the original transaction’s amount can be applied against it using the returned TAG. Multiple Tagged Authorizations or Tagged Purchases may be conducted from one Recurring Seed Purchase transaction. 41 API, Payment Pages
Tagged Purchase Sends through a request for funds to be charged to cardholder that is associated with a previous Recurring Seed transaction. Multiple Tagged Purchases can be conducted from one Recurring Seed Transaction. 30 API
Tagged Pre-Authorization Applies an authorization against the credit card number provided in a previous Recurring Seed or Recurring Seed Purchase transaction. In order to identify the previous transaction, the TAG returned in that transaction must be sent with the Tagged Authorization. The Credit Card Number and the Expiry Date must not be sent. An unlimited number of Tagged Authorizations may be applied to a specific Tag. 31 API
Tagged Completion Sends through a request for reserved funds to be charged to a cardholder. This type of transaction is associated with a previously processed Pre-Authorization or Recurring Seed transaction. Only one Tagged Completion is permitted per Recurring Seed or Pre-Authorization. 32 API
Tagged Refund Sends through a request for funds to be returned to a cardholder. This type of transaction is associated with a previously processed Purchase or Completion. 34 API
Tagged Void Sends through a void to prevent the settlement of the funds. Voids must be processed on the same day as the authorization. 33 API

Debit Transactions

Transaction Type Description Transaction Code Compatible Services
Debit Purchase Sends through sale and request for funds to be moved from cardholder’s bank account 50 API
Debit Refund Sends through a request for funds to be returned to cardholder’s bank account. Refunds should not be made an automated function or available to cardholders. 54 API
Debit Online Tagged Refund Sends through a request for funds to be returned to cardholder’s bank account based on previous Debit Purchase. 35 API

Special Transactions

Transaction Type Description Transaction Code Compatible Services
Pre-Authorization Only A type of transaction that is specific to Emergis/CT Payment. This does not apply 15% to the dollar amount for tip allocation, as with regular Pre-Authorizations. This type of pre-authorization cannot be completed. 05 API
Purchase Correction A type of transaction that is specific to Moneris. Requires a dollar amount, cardholder name, card number, card expiry, and authorization number of a previous transaction. 11 API
Refund Correction A type of transaction that is specific to Moneris. Requires a dollar amount, cardholder name, card number, card expiry, and authorization number of a previous transaction. 12 API
Secure Storage Stores card information and returns a transaction tag for later retrieval. No transaction processing is performed. At minimum, the cardholder name, card number, card expiry, amount, and reference number are required. 60 API
Transaction Details Returns information about the given transaction; requires that the transaction tag is submitted as part of the request. CR API
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk