E-xact Error Codes
Contents |
for CT Payment (formerly Telus & Emergis) Codes for Moneris Royal Bank Merchant Link (Western) Codes for TSYS (Vital) Codes for Chase Paymentech credit card declined reason codes Codes for CT Payment (formerly Telus & Emergis) Response Code Status
Atm Response Codes
Message 000 APPROVED APPROVED 050 DECLINED DECLINE Thank you. 051 DECLINED Please call your (Visa, MC, Amex) chase paymentech error codes auth. center 052 DECLINED Please call your (Visa, MC, Amex) auth. center 053 DECLINED Please call your (Visa, MC, Amex) auth. center 054 DECLINED Please call your (Visa,
Atm Response Code 068 Means
MC, Amex) auth. center 055 DECLINED Please call your (Visa, MC, Amex) auth. center 056 DECLINED PICK UP CARD 057 DECLINED HOLD CARD 058 DECLINED ERROR ACCOUNT 059 DECLINED EXPIRY ERROR 060 DECLINED Please call your (Visa, MC, Amex) auth. center 061 DECLINED Please call your (Visa, MC, Amex) auth. center 100 DECLINED NO MORE ITEMS 200 credit card processing decline codes DECLINED SYSTEM DOWN 201 DECLINED TRANSMIT ERROR 202 DECLINED INVALID MERCHANT ID 204 DECLINED Please call your (Visa, MC, Amex) auth. center 205 DECLINED INV EXPIRY DATE 206 DECLINED CARD EXPIRED 207 DECLINED INVALID MERCH ID 208 DECLINED INVALID AUTH CODE 216 DECLINED CALL AUTH CENTER 218 DECLINED CALL AUTH CENTER 219 DECLINED CALL AUTH CENTER 220 DECLINED INVALID MSG TYPE 221 DECLINED CALL AUTH CENTER 222 DECLINED CALL AUTH CENTER 224 DECLINED CALL AUTH CENTER 225 DECLINED CALL AUTH CENTER 226 DECLINED CALL CENTER 227 DECLINED CALL AMEX 228 DECLINED CALL VOICE CENTER 229 DECLINED INV CARD TYPE 230 DECLINED CALL AUTH CENTER 231 DECLINED Please call your (Visa, MC, Amex) auth. center 232 DECLINED Please call your (Visa, MC, Amex) auth. center 233 DECLINED Please call your (Visa, MC, Amex) auth. center 234 DECLINED Please call your (Visa, MC, Amex) auth. center 235 DECLINED CALL 1-800-268-7760 290 DECLINED ERROR UNKNOWN 291 DECLINED ERROR 10: FORMAT 292 DECLINED ERROR 11: MAPP 293 DECLINED ERROR 13: ACCT #
Basic Information 1.2 A Few Examples Using cURL 1.2.1 Example 1. Pre-Authorization 1.2.2 Example 2. Tagged Pre-Authorization Completion 1.2.3 Example 3. Tagged Refund 1.3 Client Libraries 2 Transaction Processing
Visa Declined Codes
Scenarios 3 Request Properties 4 Response Properties 5 SOAP Message Format 5.1 Request
Debit Card Declined Codes
Message Format 5.2 Response Message Format 6 Exception Handling 6.1 SOAP Exception 6.2 SOAP Exception Scenarios 6.3 Response - Error credit card declined code 200 Properties Appendix 1. More About Service URLs 1 Introduction The Transaction Processing API is a web service that allows third-party applications to process transactions through E-xact's system. The range of processing scenarios (Purchase, https://hostedcheckout.zendesk.com/entries/199205-Bank-Processor-Codes-FI-Codes- Refund, Pre-Authorization, etc.) enable flexible and powerful ways to implement custom business logic. E-xact also provides free client libraries that ease integration with the API. The API is available in both SOAP and REST, where the latter supports XML and JSON message formats. The same range of transaction processing scenarios is supported regardless of which style API you choose. 1.1 Basic Information The service URLs are: Endpoint https://hostedcheckout.zendesk.com/entries/231362-Transaction-Processing-API-Reference-Guide - https://api.e-xact.com/transaction WSDL - https://api.e-xact.com/transaction/wsdl IMPORTANT NOTE: If you are using our DEMO site at rpm.demo.e-xact.com with a Gateway ID of "AD...", you will need to use the Endpoint : https://api.demo.e-xact.com/transaction. Please refer to Appendix 1 for more information about legacy URLs. Two pieces of information must be provided when you submit a transaction via the API, they are: Exact ID - also known as the Gateway ID, this value identifies the Merchant and Terminal under which the transaction is to be processed Password - authenticates the API request, this value should not be exposed to the public These credentials can be submitted in two ways: as HTTP Basic Authentication user name and password values as part of the API message via the ExactID and Password properties Examples in the next section will use these methods alternately, the choice of method is up to you. 1.2 A Few Examples Using cURL The following examples submit transactions using the minimal required properties for each processing scenario. NOTE: Exact ID and Password in the request and response have been substituted with the placeholders "ExactID" and "Password". 1.2.1 Example 1. Pre-Authorization This request illustrates the following: using the SOAP style API
Appearance 4 Configuration 4.1 Payment Page: General Settings 4.2 Payment Page: Payment Types Settings 4.3 Payment Page: Receipt Page Settings 4.4 Payment Page: Receipt https://hostedcheckout.zendesk.com/entries/207209-Hosted-Checkout-Integration-Manual Emails Settings 4.5 Payment Page: Appearance Settings 4.6 Payment Page: Security Settings 4.7 Payment Page: Hash Calculator 4.8 Payment Page: Recurring 5 Character Encoding 6 Payment Form Fields 6.1 Essential Fields 6.2 Transaction and Display Fields 6.3 Order and Customer Detail Fields 6.4 Unsupported Fields and Unsupported Authorize.net Functionalities 8 Relay Response 9 Silent Post 10 Transaction Result Fields 10.1 Standard Authorize.net credit card Fields 10.2 Standard Authorize.net Fields (Credit Card Only) 10.3 E-xact Additional Fields 10.4 E-xact API Response Fields 10.5 E-xact API Response Fields (Credit Card Only) 10.6 Response Reason Codes and Text 10.7 Common Bank Response Codes 10.8 Address Verification Result Codes 10.9 CVV2 Verification Indicator Codes 10.10 CVV2 Result Codes 11 Example Payment Forms 11.1 Basic Example 11.2 Example Including Relay credit card declined Response 11.3 Resulting Payment Form 11.4 Example with Order Details 12 Implementation and Testing Guide 12.1 Generation of the Checkout Form 12.1.1 Calculating the x_fp_hash value 12.1.2 Testing the x_fp_hash calculation 12.1.3 Tying the Payment to a Particular Order 12.2 Relay Response Implementation 12.2.1 Generated HTML 12.2.2 Customer Cookies 12.2.3 Relay Response Signature 12.2.4 Sample Relay Response POST 12.2.5 Relay Response Sample Code 1 Intended Audience This document is intended for Merchants who want to understand the payment processing features of E-xact Transactions' Payment Pages service. Web developers who integrate a merchant's website with Payment Pages for payment processing. This document covers the configuration of the merchant's account at E-xact, the payment request parameters that should be sent by the merchant and how they are processed, and includes request examples. 2 Introduction A Payment Page is a securely hosted web payment form designed to accept Internet-based E-commerce transactions. With Payment Pages customers can pay with their credit cards or directly from their bank account through Interac Online. Interac Online enables a customer to pay directly from their bank account and utilizes the custome