Chase Paymentech Continue to Process a 1 00 Transaction
Supported Payment Methods and Credit/Debit Cards
Methods
| Cards
|
Mail Order/Telephone Order (MOTO) Enhancement
Aria has enhanced the Chase Paymentech integration with support for the mail/telephone order (MOTO) transaction type. This means that you will not see the 3DS challenge when you make a purchase for a customer who is not physically present at your business location and:
- You call the authorize_electronic_payment API and you set the <transaction_type>
value to 1 and pass false into the <attempt_3d_secure> field; or -
In your Direct Post configuration, you set the Transaction Type field to Single transaction mail/telephone order (MOTO) and pass false into the <attempt_3d_secure> field in your Form of Payment page.
In your Direct Post configuration, Transaction Type is now a text-only field (as shown):
The following values can be entered at the Transaction Type field:
| Value | Description |
| -1 | Use client configuration settings for "Send Transaction Type as Recurring for Initial Request Where Possible" or "Send Transaction Type as Recurring for Subsequent Request" as applicable. |
| 1 | (Chase) Single Transaction mail/telephone order (MOTO) - Designates a transaction where the account holder is not present at a merchant location and consummates the sale via the phone or through the mail. The transaction is not for recurring services or product and does not include sales that are processed via an installment plan. |
| 2 | (Chase) Recurring Transaction - Designates a transaction that represents an arrangement between an account holder and the merchant where transactions are going to occur on a periodic basis. |
| 3 | (Chase) Installment Transaction - Designates a group of transactions that originated from a single purchase where the merchant agrees to bill the account holder in installments. |
| 4 | (Chase) Deferred Transaction - Designates a transaction that represents an order with a delayed payment for a specified amount of time. |
| 5 | (Chase) Secure Electronic Commerce Transaction - Designates a transaction consummated via the Internet at a 3-D Secure capable merchant and the account holder is fully authenticated. (e.g. 3-D Secure includes Verified by Visa, Mastercard Identity Check, American Express SafeKey and Discover ProtectBuy). |
| 6 | (Chase) Non-Authenticated Electronic Commerce Transaction - Designates a transaction consummated via the Internet at a 3-D Secure capable merchant that attempted to authenticate the account holder using 3-D Secure (e.g. 3-D Secure includes Verified by Visa and Mastercard Identity Check). Verified by Visa, Mastercard Identity Check, American Express SafeKey and Discover ProtectBuy transactions in the event of:
|
| 7 | (Chase) Channel Encrypted Transaction - Designates a transaction between an account holder and a merchant consummated via the Internet where the transaction includes the use of transaction encryption such as SSL, but authentication was not performed. The account holder payment data was protected with a form of Internet security, such as SSL, but authentication was not performed. For Discover, indicates an e-commerce Card Transaction with data protection but not using ProtectBuy for Cardholder authentication. |
| 8 | (Chase) Non-Secure Electronic Commerce Transaction - Designates a transaction between an account holder and a merchant consummated via the Internet where:
|
| I | (Chase) IVR Transaction (PINless Debit only) - Designates a transaction where the account holder consummates the sale via an interactive voice response (IVR) system. |
| R | (Chase) Retail Transaction - Designates a transaction where the account holder was present at a merchant location. |
This applies to the following APIs:
- assign_supp_plan
- authorize_electronic_payment
- collect_from_account
- create_acct_complete
- create_acct_hierarchy
- create_order
- create_order_with_plans
- manage_pending_invoice
- modify_supp_plan
- replace_supp_plan
- settle_account_balance
- update_acct_complete
- update_payment_method
- validate_acct_fraud_scoring
- validate_payment_information
Batch Account Updater
The following Account Updater fields for the Chase Paymentech payment gateway are now honored at the collection group level as part of the Aria integration to support international divisions for clients (Configuration > Payments > Collection Groups):
- AU_Days_Prior_to_Invoice
- AU_Update_Interval
- AU_Cards_to_Update
- AU_Merchant_Company_Number
- AU_Division_Code_US
- AU_Division_Code
Aria has also enhanced the Chase Paymentech Account Updater by allowing configurable actions depending upon your business practices. A new Chase AU Response Code Handler Settings field called Response Code Q Action (with this response code matched to an internal Aria setting) has been added at the payment gateway (Configuration > Payments > Payment Gateways > Gateway Options) and collection group (Configuration > Payments > Collection Groups > Collection Group Options) levels.
The field appears as follows:
The following selections are available at this field:
| Selection | Description |
| Use Payment Gateway Setting | Honored at the Collection Group level. |
| No Action Required | Default selection. |
| Suspend the Payment Method | This will be honored for existing clients using this selection. |
Aria Configuration Fields
- Division Code: This field contains the Merchant ID (MID) number assigned to you by Chase Paymentech. This is your Salem Division number. The MID may also be referred to as the Transaction Division (TD) code or Presenter ID. This is a 6-digit numeric MID while the Orbital Gateway (Tampa Platform) uses a 12-digit numeric MID.
- Merchant division country code: If you are a US-based merchant, use this field to specify your country code (ISO 3166-1 alpha-3 code) to be used when processing all payments (for US and non-US cardholders). You can also specify your country code when you create or edit a collection groupcreate or edit a collection group.
Supported Features
- Card-level system overrides
- Fraud scoring and fraud filtering
- CNP: card-not-present. To process payments using card-present transactions (US only), you must set up card-present (retail transactions) with Paymentech.
- Enhanced Auths Marketing
- Identify a Cardholder Initiated Transaction (CIT) or Merchant Initiated Transaction (MIT) when processing Visa, Mastercard, American Express (AMEX) or Discover credit card payments (credit card and tokenized credit card).
- 3D Secure (Currently, 3DS 2.0 supports only Visa and Mastercard. Please contact your payment gateway representative for more information. More details follow.)
3D Secure Authentication
Steps to enable 3DS authentication for Chase Paymentech are provided below.
Payment Gateway Configuration
To configure 3DS Authentication for the Chase Paymentech payment gateway, select Configuration > Payments > Payment Gateways > Chase Paymentech and select True from the radio button shown below to enable 3DS authentication (False is the default):
The Payer Authentication Settings section appears:
Enter the following values:
| Field Name | Description |
| Authentication API URL | The API endpoint to reach the Chase JPM payment portal (200 character limit). |
| Merchant ID | This is a unique identifier issued to the merchant by the payment provider to perform 3DS authentication in the Chase JPM payment portal. |
| Authentication API Password | This is the password used to authenticate the Merchant ID. |
| 3DS Termination URL | This is the URL on the merchant website that is invoked after completing the payer authentication process. For direct post, the value should be "https://secure.<environment>.ariasystems.net/api/auth_3ds2_notification_receiver.php" where the <environment> will different for the QU, Stage, or Production environments (200 character limit). Note: The 3DS Termination URL varies depending on whether it is an API or Direct Post configuration. If using APIs, the client should use their own URL and not Aria's. If using Direct Post, the 3DS Termination URL should be Aria's. |
Press Save to retain your 3DS Authentication configuration.
Collection Group Configuration
To configure 3DS Authentication for Chase Paymentech as part of a collection group, select Configuration > Payments > Collection Groups. The following appears:
Select the Use Payment Gateway Setting radio button to use the payment gateway configuration for 3DS (this is the default). Select True from the radio button shown below to enable 3DS authentication for your collection group.
The Payer Authentication Settings section appears:
Enter the following values:
| Field Name | Description |
| Authentication API URL | The API endpoint to reach the Chase JPM payment portal (200 character limit). |
| Merchant ID | This is a unique identifier issued to the merchant by the payment provider to perform 3DS authentication in the Chase JPM payment portal. |
| Authentication API Password | This is the password used to authenticate the Merchant ID. |
| 3DS Termination URL | This is the URL on the merchant website that is invoked after completing the payer authentication process. For direct post, the value should be "https://secure.<environment>.ariasystems.net/api/auth_3ds2_notification_receiver.php" where the <environment> will different for the QU, Stage, or Production environments (200 character limit). Note: The 3DS Termination URL varies depending on whether it is an API or Direct Post configuration. If using APIs, the client should use their own URL and not Aria's. If using Direct Post, the 3DS Termination URL should be Aria's. |
Press Save to retain your 3DS Authentication configuration.
Note: The Collection Group 3DS configuration takes precedence over the Payment Gateway 3DS configuration.
API Configuration
The Chase Paymentech 3DS API configuration instructions follow, including the following output:
| Field Name | Description | Affected APIs |
| <pa_3ds_from_content> | If the issuer's Access Control Server (ACS) supports this feature, this field will receive content to populate the client's form page to enable 3DS authentication. If the issuer's ACS does not support this feature, no information for authentication will be returned to this field. | authorize_3dsecure authorize_electronic_payment validate_acct_fraud_scoring |
3D Secure Authentication for Chase Paymentech is a five-step process, as follows:
- Begin Authentication
Execute either of the following APIs:
- Submit the Device Data Collection (DDC) Form.
Note: It is the client's responsibility to provide the DDC form.
If the "authentication.3ds.methodSupported" value from Chase and their ACS is SUPPORTED, then the <pa_3ds_from_content> field will receive content to populate the client's DDC form to enable 3DS authentication. If the "authentication.3ds.methodSupported" value from Chase and their ACS is NOT SUPPORTED, no DDC form data is returned.
- Authenticate Payer
Execute the following API:
| API Name | Inputs | Outputs |
| authorize_3dsecure | <proc_payment_id> (from Step 1) | <pa_3ds_from_content> and <pa_3ds_message_version> in <proc_3dsecure_data/ proc_3d_secure_auth_data> array (containing challenge/DDC form page HTML content) |
| *<end_user_ip_address> | Default is Chase | |
| *<end_user_browser_accept_header> | ||
| *<end_user_browser_agent> | Default is Chase | |
| *<end_user_browser_color_depth> | ||
| *<end_user_browser_java_enabled_ind> | ||
| *<end_user_browser_language> | ||
| *<end_user_browser_screen_height> | ||
| *<end_user_browser_screen_width> | ||
| *<end_user_browser_timezone_offset_mins> |
*-Hidden field
- Challenge Shopper
Use the <pa_3ds_from_content> value (from step #3) in the HTML form page to perform/complete the Shopper Challenge for the 3DS 2.0. Make sure the response includes 'result/response_gatewayRecommendation.
- Authorization
Execute the following API:
| API Name | Inputs | Outputs |
| authorize_3dsecure | <proc_payment_id> (from Step 1) | <pa_3ds_from_content> and |
SCA 3DS Exemption
For Chase Paymentech, a setting has been added under Options at the payment gateway and collection group level for a low-value payment strong customer authentication (SCA) exemption (for 3DS-enabled merchants). The default selection for this field is No Exemption. Using this setting, a Chase customer will not get a pop-up confirmation message for the 3DS transaction under the exempted amount and currency, which will ensure more seamless transaction processing. To access the Chase Paymentech gateway, navigate as follows in the Aria UI: Configuration > Payments > [Payment Gateways][Collection Groups].
Create a new Payment Gateway or Collection Group and select Low Value Payment from the Exemption Type field as shown:
Note: Clients need to work with Chase for enabling the low amount value SCA exemption feature for their merchants.
For Direct Post, an SCA Exemption textbox field has been introduced in the USS Reg Configuration (Configuration > Client Settings > USS Reg Configuration), as shown:
Clients can specify the following values:
- 0 – Do not apply exemption. Process transaction via 3D Secure.
- 1 – Apply the exemption and skip 3D Secure Authorization.
- -1 – Use Payment Gateway or Collection Group settings for exemption rules.
For APIs, client can specify low amount exemptions in the <proc_field_override> array of the following APIs:
- authorize_electronic_payment
- validate_acct_fraud_scoring
Apple Pay Payment Method Now Included In Chase Paymentech Integration
Aria is excited to introduce Apple Pay as a digital payment method to our Chase Paymentech integration. Tokenized payments are supported for the Visa®, Mastercard®, American Express® and Discover® card types.
To configure Apple Pay for Chase Paymentech, navigate to the Apple Pay tab as shown (Configuration > Payments > Payment Gateways/Collection Groups [Chase Paymentech]). Download the Certificate Signing Request (.csr) file (Step 1). After downloading the .csr file, perform the following (Step 2):
- Visit the Apple Pay portal.
- Log into your merchant account.
- Attach the CSR file.
- Get the .cer format file.
After obtaining the .cer file, upload the file from the Apple Pay tab (Step 3) to complete the pre-requisite steps for making Apple Pay payments.
After generating and uploading the .cer format file to enable Apple Pay payments through Chase Paymentech, you can contact Aria with the Apple Pay payload generated outside of Aria. To accomplish this, an input field has been added to the existing record_alternative_payment API.
| Input Field Name | Description |
| <external_payment_payload> | This accepts the Apple Pay encrypted payment payload. Using your payment processing certificate, Aria will decrypt the payload and store the token for future payments. |
While executing the record_alternative_ payment API (with
In addition to the newly added
| Input Field Name | Description |
| <primary_payment_method_ind> | Indicates the Apple Pay billing record to be created as primary payment method for the billing group mapped in the passed statement number. The default is 0. If we pass as '1', then the billing record will be created as primary pay method for the billing group associated with the statement number. |
As a reminder, Apple Pay tokenized payments are supported for the Visa®, Mastercard®, American Express® and Discover® card types.
Links
- Chase/JP Morgan Developer Center
Regarding Processor/Gateway Integration Certifications
Regarding Processor- and Gateway-specific Information
medeirosaftefuld66.blogspot.com
Source: https://developer.ariasystems.net/UserDocumentation/07Payments_and_Credits/Payment_Gateways/06_Supported_Payment_Gateways_and_Payment_Methods/Chase_Paymentech
0 Response to "Chase Paymentech Continue to Process a 1 00 Transaction"
Postar um comentário