Chase Paymentech
Chase Paymentech is a U.S.-based payment service provider and merchant acquiring business that is part of J.P. Morgan Chase, a multinational finance corporation. In addition to its payment services, Chase Paymentech provides associated business services such as analytics, payment fraud detection, and data security.
Features
- Tokenization
- Credit Card Processing (Authorization, Capture, Cancel, Reversal)
- Debit Card Processing (Authorization, Capture, Cancel, Reversal)
- 3DS Secure 1.0/2.0
- Refunds (Full and Partial)
- Level 2/3 Data
- Account Updater (Batch or Real Time)
- Soft Descriptor
UI Configuration/Processing Options Tab
Screen shot of UI Processing Options tab with field names/descriptions
Supported Functionality
Additional details on available features
Basic Supported Features For Smart Payments
With this release, Chase Paymentech is now included as part of Aria's Smart Payments. Chase Paymentech Basic Smart Payments features include the following:
- Credit Card and Tokenized Credit Card online payments, including the following card brands:
- VISA
- Mastercard
- American Express
- Discover
- Diners Club/Carte Blanche
- International Maestro
- China UnionPay (for tokenized cards - pay method 13)
- Payment Authorization for Chase Online payments using a credit card or token
- Query Token action using the token (<bill_agreement_id>)
- Payment Capture of previously authorized transactions
- Credit Card Authorization Reversal (implemented via the Aria UI and the reverse_authorized_electronic_payment_m API)
- Refund of a previously authorized transaction back to the customer's original method of payment
- Soft descriptor support for descriptions accompanying credit/debit transactions to appear on customer's bank statements for Online payments
- 3DS Authentication for VISA and Mastercard payments (settlement in batch)
- Fraud scoring and fraud filtering (including 3DS support for VISA and Mastercard using the validate_acct_fraud_scoring_m API)
- CIT (Customer-Initiated Transaction)/MIT (Merchant-Initiated Transaction) Indicator (implemented through the <recurring_processing_model_ind> input of the authorize_electronic_payment_m API for Online payments)
- Transaction logging supported for the following actions: create token, authorization, payment, and authorization reversal
- CIT/MIT Recurring Indicators via the <recurring_processing_model_ind> input you can specify in the following APIs to flag recurring transactions as desired:
Note: The Recurring Payment indicator can now be overridden through the Collection Group and Payment Gateway configuration settings (Configuration > Payments > [Payment Gateways/Collection Groups] > Processing Options tab > Recurring Options).
Advanced Supported Features for Smart Payments
As part of Aria's Smart Payments integration with Chase Paymentech, advanced features, including Level 2 and Level 3 payment data, are now supported. Support for the ACH, BACS and SEPA payment methods along with Strong Customer Authentication (SCA) exemptions have also been added to the set of advanced features for Chase Paymentech.
Additional details are provided as follows:
- Automated Clearing House (ACH) online payments are available specifically for the U.S. and Canada, mapped to payment method 2). ACH batch settlement is also included.
- Single Euro Payments Area (SEPA) direct debit online payments are now supported also (payment method 26, IBAN indicator: 1). SEPA batch settlement is also included.
- Bankers' Automated Clearing Services (BACS) direct debit online payments are now supported also (payment method 26, IBAN indicator: 0). BACS batch settlement is also included for one-time and recurring online transactions.
- For the Real-Time Account Updater (VISA only), Aria supports the following response codes from Chase Paymentech:
- J—New card number and new expiry date found
- A—New card number found
- E—New expiry date found
- Q—Contact cardholder (similar to the Batch Account Updater in the legacy Chase Paymentech integration, the Processing Option “Response Code Q Action” in the Collection Group/Payment Gateway configuration will apply to Real-Time account updates as well).
- Low-value payment SCA exemptions are now supported for eligible transactions within Chase Paymentech Smart Payments based on the SCA exemption type indicator at the Payment Gateway or Collection Group level (this is for batch settlement; the low-value threshold is based on issuer policies).
Chase Paymentech's Advanced features also includes Level 2 and Level 2 data support, as shown:
| Level 2/Level 3 | Line Item Level/Order Level | Record | Card Brands |
|---|---|---|---|
| Procurement Level 2 (Batch) | |||
| Line Item Level Data | PPC002 | All card brands* | |
| Procurement Level 3 (Batch) | |||
| Order Level Record Data | PP0001 | VISA, Mastercard | |
| Line Item Level Data | PP1, Record 1 | Mastercard | |
| PP2, Record 2 | |||
| PP1002, Record 1 | VISA, Discover, Diner's Club | ||
| PP2002, Record 2 |
*—Only Level 2 data supported for American Express
Apple Pay Payments
The following Apple Pay payment types are supported as shown:
| Apple Pay type | Online | Batch |
|---|---|---|
| Initial and subsequent payments | X | |
| External payment payloads - one time and recurring transactions (pay method=47) | X | |
| Refunding a previously captured Apple Pay transaction back to the customer's original payment method | X | X |
Apple Pay Shipping Contact Details
The following Apple Pay shipping contact details are now extracted and stored within Aria when recording a payment:
- ship_fname
- ship_lname
- ship_addr_ln1
- ship_addr_ln2
- ship_addr_ln3
- ship_city
- ship_state
- ship_zip
- ship_country
- ship_email
- ship_phone
Note: These fields will be populated only if the corresponding data is present in the external payment payload.
<proc_status_text> API Note
The <proc_status_text>
Supported Actions for Batch AU Receiver
The following actions are now supported for the Chase Batch Account Updater (AU) Receiver:
| Letter | Action | Feature |
|---|---|---|
| A | Update new card number |
|
| C | Close account advice |
|
| E | Update expiry date |
|
| Q | Contact cardholder advice |
|
Response File Error Handling
Files with the following error codes are handled and logged appropriately:
| Code | Definition | Status | Action |
|---|---|---|---|
| 6782 | Batch file name already exists in the database | Error | Fix |
| 6785 | User is currently set to inactive in the database | Error | Resend |
| 6787 | The sender has sent more than one file per zip | Error | Fix |
| 6799 | The name of the zip file and the payload file zipped inside do not match | Error | Fix |
| 6801 | Zip file needs to be encrypted | Error | Fix |
| 6810 | File name is too long | Error | Fix |
| 6815 | Presented ID is not valid for this user | Error | Fix |
Other Features
- Non-ASCII characters sent in the Chase batch are now replaced with a dot (.) per the Chase batch specification. This applies to the following fields:
- first_name
- last_name
- middle_initial
- address1
- address2
- city
- state
- zip
- country
- Aria now honors multiple company codes for Chase configured within the payment gateway and collection account group levels. All the collection account groups (plus the payment gateway) are grouped based on the company code and sent as a file per company code basis.
- Aria also now displays enhanced authorization information in API responses and also in the UI using additional information received in the CT02 record from Chase, including the following fields:
- prepaid_ind
- prepaid_card_type
- affluence_type
- issuing_country
- card_product_type
- signature_debit_ind
- pinless_debit_ind
- durbin_regulated_ind