Payeezy Gateway Guide

close

Services and Compatibility

Payment Gateway Company Name:
Payeezy
Services that work with Spreedly:
  • Payeezy
Supported operations:
Purchase, Authorize, Capture, Refund, Void, Verify, Store
Supported payment types:
Credit Card, Bank Account
Regions:
North America

Authentication and Security

Specific names for credentials:
Api Key, Api Token, Api Secret

Onboarding Merchants in:

Additional Notes

Using Visa and Mastercard cards retained with Spreedly falls under Visa Card-on-File regulations.

Using the store method requires an additional gateway specific field required by Payeezy. See the specific fields for Store below for more information.

If you plan on using bank accounts as a payment method for Payeezy transactions, you must send a couple additional gateway specific fields required by Payeezy but not Spreedly. Specifically client_id_type, client_id_number, and client_email. See the eCheck gateway specific fields for more information.

For First Data’s older Payeezy gateway, also called Global Gateway e4 (GGE4) please go to the documentation here. This is the current Payeezy release (REST API). This gateway also has connectivity to First Data’s International Payment Gateway (IPG) Payeezy UK for Europe, India, Brazil, and Australia.

Endpoint: https://api.payeezy.com/v1

Adding a Payeezy gateway

To add a Payeezy gateway:


curl https://core.spreedly.com/v1/gateways.xml \
  -u 'C7cRfNJGODKh4Iu5Ox3PToKjniY:4UIuWybmdythfNGPqAqyQnYha6s451ri0fYAo4p3drZUi7q2Jf4b7HKg8etDtoKJ' \
  -H 'Content-Type: application/xml' \
  -d '<gateway>
        <gateway_type>payeezy</gateway_type>
        <api_key>Your api key</api_key>
        <api_secret>Your api secret</api_secret>
        <api_token>Your api token</api_token>
      </gateway>'

<gateway>
  <token>6WKsmatnIemL4KZWOgRGcNE7iOO</token>
  <gateway_type>payeezy</gateway_type>
  <name>Payeezy</name>
  <description nil="true"/>
  <api_key>Your api key</api_key>
  <api_token>Your api token</api_token>
  <characteristics>
    <supports_purchase type="boolean">true</supports_purchase>
    <supports_authorize type="boolean">true</supports_authorize>
    <supports_capture type="boolean">true</supports_capture>
    <supports_credit type="boolean">true</supports_credit>
    <supports_general_credit type="boolean">false</supports_general_credit>
    <supports_void type="boolean">true</supports_void>
    <supports_verify type="boolean">true</supports_verify>
    <supports_reference_purchase type="boolean">false</supports_reference_purchase>
    <supports_purchase_via_preauthorization type="boolean">false</supports_purchase_via_preauthorization>
    <supports_offsite_purchase type="boolean">false</supports_offsite_purchase>
    <supports_offsite_authorize type="boolean">false</supports_offsite_authorize>
    <supports_3dsecure_purchase type="boolean">false</supports_3dsecure_purchase>
    <supports_3dsecure_authorize type="boolean">false</supports_3dsecure_authorize>
    <supports_store type="boolean">true</supports_store>
    <supports_remove type="boolean">false</supports_remove>
    <supports_fraud_review type="boolean">false</supports_fraud_review>
  </characteristics>
  <credentials>
    <credential>
      <name>api_key</name>
      <value>Your api key</value>
    </credential>
    <credential>
      <name>api_token</name>
      <value>Your api token</value>
    </credential>
  </credentials>
  <gateway_specific_fields>
    <gateway_specific_field>soft_descriptors</gateway_specific_field>
    <gateway_specific_field>customer_id_type</gateway_specific_field>
    <gateway_specific_field>customer_id_number</gateway_specific_field>
    <gateway_specific_field>client_email</gateway_specific_field>
    <gateway_specific_field>ta_token</gateway_specific_field>
    <gateway_specific_field>reversal_id</gateway_specific_field>
    <gateway_specific_field>cardbrand_original_transaction_id</gateway_specific_field>
    <gateway_specific_field>sequence</gateway_specific_field>
    <gateway_specific_field>is_scheduled</gateway_specific_field>
    <gateway_specific_field>initiator</gateway_specific_field>
    <gateway_specific_field>auth_type_override</gateway_specific_field>
  </gateway_specific_fields>
  <payment_methods>
    <payment_method>credit_card</payment_method>
    <payment_method>bank_account</payment_method>
    <payment_method>third_party_token</payment_method>
  </payment_methods>
  <state>retained</state>
  <redacted type="boolean">false</redacted>
  <created_at type="dateTime">2018-12-17T14:13:55Z</created_at>
  <updated_at type="dateTime">2018-12-17T14:13:55Z</updated_at>
</gateway>

Optional Gateway Specific Fields

When interacting with a Payeezy gateway to run transactions, there are some gateway specific fields you can specify.


curl https://core.spreedly.com/v1/gateways/LlkjmEk0xNkcWrNixXa1fvNoTP4/purchase.xml \
  -u 'C7cRfNJGODKh4Iu5Ox3PToKjniY:4UIuWybmdythfNGPqAqyQnYha6s451ri0fYAo4p3drZUi7q2Jf4b7HKg8etDtoKJ' \
  -H 'Content-Type: application/xml' \
  -d '<transaction>
        <payment_method_token>56wyNnSmuA6CWYP7w0MiYCVIbW6</payment_method_token>
        <amount>100</amount>
        <currency_code>USD</currency_code>
        <gateway_specific_fields>
          <payeezy>
            <reversal_id>the-reversal-id</reversal_id>
            <customer_id_type>The customer id type</customer_id_type>
            <customer_id_number>The customer id number</customer_id_number>
            <client_email>The client email</client_email>
            <soft_descriptors>
              <dba_name>Caddyshack</dba_name>
              <street>1234 Any Street</street>
              <city>Durham</city>
              <region>North Carolina</region>
              <mid>mid_1234</mid>
              <mcc>mcc_5678</mcc>
              <postal_code>27701</postal_code>
              <country_code>US</country_code>
              <merchant_contact_info>8885551212</merchant_contact_info>
            </soft_descriptors>
            <ta_token>ta_token</ta_token>
            <cardbrand_original_transaction_id>abc123</cardbrand_original_transaction_id>
            <sequence>FIRST</sequence>
            <is_scheduled>true</is_scheduled>
            <initiator>MERCHANT</initiator>
            <auth_type_override>A</auth_type_override>
          </payeezy>
        </gateway_specific_fields>
      </transaction>'

<transaction>
  <on_test_gateway type="boolean">true</on_test_gateway>
  <created_at type="dateTime">2018-12-17T14:27:01Z</created_at>
  <updated_at type="dateTime">2018-12-17T14:27:01Z</updated_at>
  <succeeded type="boolean">true</succeeded>
  <state>succeeded</state>
  <token>7x0gCwx1TkbjTaVmkwhyOyCGgQW</token>
  <transaction_type>Purchase</transaction_type>
  <order_id nil="true"/>
  <ip nil="true"/>
  <description nil="true"/>
  <email nil="true"/>
  <merchant_name_descriptor nil="true"/>
  <merchant_location_descriptor nil="true"/>
  <gateway_specific_fields>
    <payeezy>
      <reversal_id>the-reversal-id</reversal_id>
      <customer_id_type>The customer id type</customer_id_type>
      <customer_id_number>The customer id number</customer_id_number>
      <client_email>The client email</client_email>
      <soft_descriptors>
        <dba_name>Caddyshack</dba_name>
        <street>1234 Any Street</street>
        <city>Durham</city>
        <region>North Carolina</region>
        <mid>mid_1234</mid>
        <mcc>mcc_5678</mcc>
        <postal_code>27701</postal_code>
        <country_code>US</country_code>
        <merchant_contact_info>8885551212</merchant_contact_info>
      </soft_descriptors>
      <ta_token>ta_token</ta_token>
      <cardbrand_original_transaction_id>abc123</cardbrand_original_transaction_id>
      <sequence>FIRST</sequence>
      <is_scheduled>true</is_scheduled>
      <initiator>MERCHANT</initiator>
      <auth_type_override>A</auth_type_override>
    </payeezy>
  </gateway_specific_fields>
  <gateway_specific_response_fields>
  </gateway_specific_response_fields>
  <gateway_transaction_id>53</gateway_transaction_id>
  <gateway_latency_ms type="integer">20</gateway_latency_ms>
  <amount type="integer">100</amount>
  <currency_code>USD</currency_code>
  <retain_on_success type="boolean">false</retain_on_success>
  <payment_method_added type="boolean">false</payment_method_added>
  <message key="messages.transaction_succeeded">Succeeded!</message>
  <gateway_token>T11bJAANtTWnxl36GYjKWvbNK0g</gateway_token>
  <gateway_type>test</gateway_type>
  <shipping_address>
    <name>Newfirst Newlast</name>
    <address1 nil="true"/>
    <address2 nil="true"/>
    <city nil="true"/>
    <state nil="true"/>
    <zip nil="true"/>
    <country nil="true"/>
    <phone_number nil="true"/>
  </shipping_address>
  <response>
    <success type="boolean">true</success>
    <message>Successful purchase</message>
    <avs_code nil="true"/>
    <avs_message nil="true"/>
    <cvv_code nil="true"/>
    <cvv_message nil="true"/>
    <pending type="boolean">false</pending>
    <result_unknown type="boolean">false</result_unknown>
    <error_code nil="true"/>
    <error_detail nil="true"/>
    <cancelled type="boolean">false</cancelled>
    <fraud_review nil="true"/>
    <created_at type="dateTime">2018-12-17T14:27:01Z</created_at>
    <updated_at type="dateTime">2018-12-17T14:27:01Z</updated_at>
  </response>
  <api_urls>
  </api_urls>
  <payment_method>
    <token>1rpKvP8zOUhj4Y9EDrIoIYQzzD5</token>
    <created_at type="dateTime">2017-06-26T17:04:38Z</created_at>
    <updated_at type="dateTime">2018-12-14T13:49:32Z</updated_at>
    <email>joey@example.com</email>
    <data>
      <my_payment_method_identifier>448</my_payment_method_identifier>
      <extra_stuff>
        <some_other_things>Can be anything really</some_other_things>
      </extra_stuff>
    </data>
    <storage_state>retained</storage_state>
    <test type="boolean">true</test>
    <metadata>
      <key>string value</key>
    </metadata>
    <last_four_digits>1111</last_four_digits>
    <first_six_digits>411111</first_six_digits>
    <card_type>visa</card_type>
    <first_name>Newfirst</first_name>
    <last_name>Newlast</last_name>
    <month type="integer">3</month>
    <year type="integer">2032</year>
    <address1 nil="true"/>
    <address2 nil="true"/>
    <city nil="true"/>
    <state nil="true"/>
    <zip nil="true"/>
    <country nil="true"/>
    <phone_number nil="true"/>
    <company nil="true"/>
    <full_name>Newfirst Newlast</full_name>
    <eligible_for_card_updater nil="true"/>
    <shipping_address1 nil="true"/>
    <shipping_address2 nil="true"/>
    <shipping_city nil="true"/>
    <shipping_state nil="true"/>
    <shipping_zip nil="true"/>
    <shipping_country nil="true"/>
    <shipping_phone_number nil="true"/>
    <payment_method_type>credit_card</payment_method_type>
    <errors>
    </errors>
    <verification_value></verification_value>
    <number>XXXX-XXXX-XXXX-1111</number>
    <fingerprint>e3cef43464fc832f6e04f187df25af497994</fingerprint>
  </payment_method>
</transaction>

Visa Card-on-File

Complying with Visa Card-on-File regulations requires flagging when card information that is stored with an intermediary is used for a transaction. This applies to Visa and Mastercard cards retained with Spreedly. Payeezy implementation of this flag requires the use of some of the following gateway specific fields: cardbrand_original_transaction_id, sequence, is_scheduled, initiator and auth_type_override. Please see Payeezy docs for more information.

Timeout Reversals

The reversal_id field can be added to any authorize or purchase transaction. In the event of a timeout, the same reversal_id can then be specified via void to reverse the transaction.

Soft Descriptors

You can specify soft_descriptors to pass in dynamic soft descriptor data for a transaction. Please refer Payeezy docs for relevant fields.

eCheck specific fields

Transactions using a bank account payment method require some additional data. Specifically, customer_id_type, customer_id_number, and client_email.

If client_email is not provided, and there is an email already associated with the bank account payment method, that email will be used.

See the Payeezy eCheck docs for more information.

Specific fields for Store

US Merchants will receive a Transarmor multi-use token when the store method is used to tokenize a credit card.

A gateway specific field is required for this:

  • ta_token

Please refer to Payeezy documentation for instructions on obtaining these values.

Gateway specific response fields

After a successful store transaction, Payeezy will return card_type, card_name, card_exp_date and a token_value. All of these values will need to be used if you intend to use the token outside of the Spreedly API.

You can find this information in gateway_specific_response_fields. For example, a transaction could have the following:

<transaction>
  <token>LgpTNGjsWQs9DwdxcbreUVz0R8p</token>
  <transaction_type>Store</transaction_type>
  <gateway_specific_response_fields>
    <Payeezy>
      <card_type>Visa</card_type>
      <card_name>Tony Stark</card_name>
      <card_exp_date>12/20</card_exp_date>
      <token_value>ABC1234</token_value>
    </Payeezy>
  </gateway_specific_response_fields>
</transaction>

See the Payeezy Tokenization Docs for more information