Chase Paymentech

Chase Paymentech has some special integration requirements. Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications described below.

Specifications for Card-based Transactions

The following table lists the integration specifications for Chase Paymentech.

SpecificationsDetails
Minimum PaymentsOS API Version1.1.0
Requests
  • Authorize
  • Capture (including multiple/partial)
  • Charge
  • Credit
  • Refund (including multiple/partial)
  • Void. If you void a Capture, make sure to do so before the nightly batch. Else the Void will fail.
Supported Void types:
  • Block before capture: Funds are unfrozen according to the issuing bank's transaction expiration time, and capture is blocked.
  • Reversal: This type of Void unfreezes the funds immediately.
The type of Void request that is invoked is determined by the onlineReversalIndicator field, which you may optionally pass in the provider_specific_data object of the Void request. For an example, use the Bodybuilder to generate a Void request with optional fields.
CurrenciesFor charging a customer:
DZD, ARS, AMD, AUD, BDT, BZD, BOB, BWP, BRL, GBP, BND, BGN, BIF, XOF, XAF, CAD, KHR, CLP, CNY, COP, KMF, CRC, CZK, DKK, DJF, DOP, EGP, ETB, EUR, GEL, GTQ, HNL, HKD, HUF, INR, IDR, ILS, JMD, JPY, KZT, KES, KGS, LBP, MOP, MYR, MUR, MXN, MDL, MAD, NAD, NPR, NZD, NIO, NGN, NOK, PKR, PAB, PYG, PEN, PHP, PLN, QAR, RUB, RWF, SAR, SGD, SOS, ZAR, KRW, LKR, SEK, CHF, TWD, TZS, THB, TOP, TTD, TRY, UGX, UAH, AED, UYU, USD, UZS, YER, AZN, BYN, GHS, GNF, ISK, MGA, MZN, RON, VES, VND
For settlements:
CAD, GBP, EUR, AUD, USD
Payment Methods
  • American Express
  • ChaseNet
  • DISCOVER
  • Discover Diners
  • JCB
  • MASTERCARD
  • VISA
Transaction Processing without CVVSupported
3DS RedirectionNot supported

Configurations

The following table lists the configurations that are specific to Chase Paymentech.

ConfigurationRequired/Optional
In the PaymentsOS Control Center, configure the following credentials:
  • merchant_id: The Gateway merchant account number, assigned by ChasePaymentech. Note: Only one currency can be associated with one merchant_id.
  • terminal_id (configuring this is optional): The Terminal ID assigned by Chase Paymentech. Valid range of values: a number from 000 to 999. Default if not configured is 001.
  • bin: The transaction routing definition, assigned by Chase Paymentech. Possible values:STRATUS or TANDEM.
You should have received a set of test credentials for each currency that you intend to use, when you created your Chase Paymentech account. Use these credentials to create one provider configuration per currency, in the PaymentsOS test environment.
Required
In your Chase Paymentech account, configure the Auto Settle time and timezone fields. This must be configured to prevent transactions from remaining un-settled ('Open Batch').Required
In your Chase Paymentech account, connect the Zooz submitter ID to your account. The submitter ID is 258071.Contact Chase Paymentech support for assistance.Required
In your Chase Paymentech account, set Card Verification Data (CVD) as optional or mandatory (this is also known as as CVV2, CVC2, or CID). In addition, enable CVV verification and determine whether a failed verification should cause the request to fail as well. Note that if you enabled CVV verification, you will receive the status of the verification in theadditional_detailsobject in the request response data.Optional
In your Chase Paymentech account, enable AVS verification (full AVS or zip-code only AVS) and determine whether a failed verification should cause the request to fail. Note that if you enabled AVS verification, you will receive the status of the verification in the additional_detailsobject in the request response data.Optional
In your Chase Paymentech account, confgure your account to support a statement soft descriptor sent in a transaction request. Use the Bodybuilder to generate a sample Create Payment request that includes a statement soft descriptor.Optional

Sample Requests

Use the bodybuilder to create a sample request body for each request type.

Response Data

In the response to a transaction request, you will also receive:

  • The status of the CVV and AVS verification (if enabled in your Chase Paymentech account)

  • An indication whether level 2 and 3 data was sent.

CVV and AVS Verification Response

In your Chase Paymentech account, you can enable CVV and AVS verification and determine whether a failed verification should cause the request to fail as well. If a CVV check is performed, you will receive the status of the verification in the CVV2RespCode field of additional_details object in the request response data:

...
{
  "provider_data": {
    ...
    "additional_information": {
      "CVV2RespCode": "M"
      ...
    },
  }
},
...

The CVV2RespCode can be one of the following values:

  • M: CVV Match
  • N: CVV No Match Error
  • P: Not processed
  • S: Should have been present
  • U: Unsupported by issuer/issuer unable to process request
  • I: Invalid
  • Y: Invalid
  • blank: Not applicable (non-Visa)

If an AVS verification was done, you will receive the status of the verification in the avs_code field of the provider_data object:

...
{
  "provider_data": {
    ...
    "avs_code": "A"
    ...
  }
},
...

For an overview of possible AVS codes, see AVS Response Codes.

Level 2 and 3 Data Response

Chase Paymentech accepts level 2 and 3 data fields in a Create Capture request (use the Bodybuilder to generate a sample Create Capture request that includes level 2 and 3 data). The response of the Create Capture request will let you know whether level 2 or 3 data was sent:

...
{
  "provider_data": {
    ...
    "additional_information": {
      "level_2_3_sent": "true" // true if sent; otherwise false
      ...
    },
  }
},
...

Testing

Follow the PaymentsOS recommended testing procedures.

results matching ""

    No results matching ""