Transaction Types Available

First Data’s Payeezy Gateway offers a wide range of transaction types. Below is an extensive list of Transaction Types available. If interested in supporting additional entitlement(s), please contact your Relationship Manager/Account Manager for more details.

POS Transaction Types:

Transaction Types available by logging into your Payeezy Gateway Real Time Payment account, navigating to the POS section, and selecting the Transaction Type drop down button. See example below:

The Payeezy Gateway POS currently offers the following Transaction Types:

  • Purchase
  • Void
  • Refund
  • Pre-Authorization
  • Forced Post

Additional Processing Features:

  • Quick Key
    • Only applicable to Recurring Payments, can support 250 transactions under a CSV file and the upload time may very
    • To learn more about the Quick Key

To learn more about the Transaction Types available within the Payeezy Gateway Real Time Payment Manager (RPM), please log into your Payeezy Gateway RPM account or navigate to the Transactions Section details URL. 

API Transaction Types:

Standard Transaction Types:

  • Purchase
  • Pre-Authorization
  • Refund
  • Void
  • Tagged

Additional Processing Features: All features, unless otherwise noted, will require Web Service API v9 or higher. For HMAC, use v12 or higher

  • PayPal
  • Gift Cards (with ValueLink)
  • Checks (with Telecheck) v13
  • Debit Bill Pay
  • Special Payment v21
  • Visa Checkout v22
  • MasterPass v24
  • Fees v18
  • Dynamic Currency Conversion v18
  • Dynamic Pricing v18
  • Level 2 and 3 transactions v9
  • Soft Descriptors v11

To learn more about API Transaction Types, please visit the First Data Payeezy Gateway Web Service API Reference Guide, here: https://support.payeezy.com/hc/en-us/articles/206601408-First-Data-Payeezy-Gateway-Web-Service-API-Reference-Guide#3 

 

Hosted Checkout Transaction Types:

HCO offers 2 transaction types to the merchant. 

  • Purchase
  • Authorization

Additional Processing Features:

  • Gift Cards (with ValueLink)
  • Checks (with Telecheck)
  • Visa Checkout
  • PayPal Order (if merchant is enabled)
  • Fees
  • Dynamic Currency Conversion*
  • Dynamic Pricing*
  • Level 2 and 3 transactions
  • Soft Descriptors*
  • Recurring
  • Masterpass

*Omaha excluded

To learn more about HCO Transaction Types, please visit: https://support.payeezy.com/hc/en-us/articles/203992129-Hosted-Checkout-Payment-Pages-Integration-Manual#6.2

 

Transaction Types Available

Payeezy Gateway 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 a sale which will be charged to the cardholder account and ready for settlement.

00

API, Recurring,

Payment Pages, POS,

Quick Key

Pre - Authorization

Sends a sale which will be charged to the cardholder account, transaction is not ready for settlement, must run a “Tag Completion”.

01

API, Recurring,

Payment Pages, POS

Refund

Sends a request for funds to be returned to the

Cardholder; refunds should be ran on settled transactions.

04

API, Recurring, POS, Quick Key??

 

Void

Sends a transaction to cancel out a Purchase /Pre-authorization/ Refund. Void can only be run on transactions that have not settled.

13

API, POS

 

 

 

Forced Post

Completes a

transaction that was

not authorized on

PGW’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.

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

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 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.

3

 

API

Note: Web Service API v9 or higher. For HMAC, use v12 or higher

 

 

Debit Bill Payment Transactions

Only for STAR, NYCE, and PULSE debit networks. Processed with the same structure as credit card transactions, while specifying “Debit Bill Pay” as the “credit_card_type” property

Transaction Type

Description

Transaction Code

Compatible Services

Purchase

Sends a payment which will be debited from a cardholder’s account and ready for settlement.

 

00

Web Service API v9 or higher. For HMAC, use v12 or higher

Void

Sends a transaction to cancel out a previous Purchase transaction; must be completed within 90 minutes of the Purchase transaction that has not settled, afterwards, a refund would be required

 

33

Web Service API v9 or higher. For HMAC, use v12 or higher

Refund

Sends a request for funds to be returned to the Cardholder from a previous Purchase transaction

 

34

Web Service API v9 or higher. For HMAC, use v12 or higher

Powered by Zendesk