Using Tokens to Store Credit Card Data

E-xact Transactions is a proponent of a “Non Storing” model for its customers. In this model, the merchant does not retain a copy of the credit card number after it has initially been verified through E-xact. This initial transaction is referred to as a “Seed” transaction. Seed transactions are sent like a normal transaction but have a specific transaction Type. These transactions are sent to the banking networks where the card number is authorized for the amount specified. In doing so, the merchant can be assured that the card is valid and has sufficient funds. In all cases, E-xact returns a unique TAG (sometimes called a "Token") for all its transaction. This TAG can be used to identify the transaction and therefore the card number used. With this TAG, the merchant can apply subsequent transactions against the original card number without having to retain it.

A relationship can also be defined between different business units that do not share the same merchant number. In doing so, TAGS can be utilized across an entire enterprise.

As an extra measure of security, the authorization number of the original transaction must be provided with the secondary (Tagged) transaction.

Tagged Transaction Types

Recurring Seed Authorization (40)

Applies an authorization against the credit card provided. The Cardholder’s “limit to buy” is decreased by the specified amount but no funds are settled. A Single Completion or Tagged Completion can be applied to this transaction within the allotted time. An unlimited number of Tagged Authorizations or Tagged Purchases may be associated with a Recurring Seed.

Recurring Seed Purchase (41)

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 transactions amount can be applied against it using the returned TAG. An unlimited number of Tagged Authorizations or Tagged Purchases may be associated with it using the returned TAG.

Tagged Purchase (30)

Applies a Purchase 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 purchase. The Credit Card Number and the Expiry Date must not be sent. An unlimited amount of Tagged Purchases may be applied to a specific Recurring Seed or Recurring Seed Purchase.

Tagged Authorization (31)

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 amount of Tagged Authorization may be applied to a specific Recurring Seed or Recurring Seed Purchase.

Tagged Completion (32)

Settles funds previously held by a Recurring Seed Authorization or Pre-Authorized Transaction. In order to identify the previous transaction, the TAG returned in that transaction must be sent with the Tagged Completion. The Credit Card Number and the Expiry Date must not be sent. Only a single Tagged Completion may be sent against a single Pre-Authorized transaction. The amount is also limited by the amount of the original transaction.

Tagged Refund (34)

Returns funds to a cardholder based the credit card number used in a previous Payment transaction. In order to identify the previous transaction, the TAG returned in that transaction must be sent with the Tagged Refund. The Credit Card Number and the Expiry Date must not be sent. Many Tagged Refunds may be sent against a single transaction as long as the total dollar amount does not exceed the original Payment transaction Amount.

Tagged VOID (33)

Voids a previously approved transaction. Will be declined if the current settlement batch has been closed. In order to identify the previous transaction, the TAG returned in that transaction must be sent with the Tagged VOID. The Credit Card Number and the Expiry Date must not be sent. Only one Tagged VOID may be sent against a single transaction.

Check out our Transaction Web Service at: https://hostedcheckout.zendesk.com/entries/231362-transaction-processing-api-reference-guide.