Free Websites at Nation2.com
Translate this Page




Total Visits: 421

Transmission data parser failure authorization cod

Transmission data parser failure authorization cod

Untitled




Download: Transmission data parser failure authorization code is malformed or invalid




Check the property name, case, and spelling. Initial aim for creating this code was using it for digital payment systems however this is not used currently. The Transmission Scheduler allows multiple modules to operate in parallel and shared fashion that depends on transmit data traffic.


transmission data parser failure authorization code is malformed or invalid

PENDING Transaction approved ECheck transactions. In the presence of secret sharing, the computation of the signature would require consensus of the share holders, and ideally should be done without revealing the private key.


transmission data parser failure authorization code is malformed or invalid

Family - For example, if a web.

 

Gateway Response Codes The current at the time of this release response codes for the supported Gateways are listed below. Please see the individual specifications for each Gateway available from the Gateway itself for an updated list of these codes. You must authorize the order before requesting a capture 40 The requested credit amount must equal the original transaction amount 48 The transaction amount exceeds the bank's limit of {. Please split the transaction so that the transaction amount for each transaction is less than this amount. Verify it is a card that you accept 54 Message returned from bank reason for decline-not always populated 55 Not a valid user for external processing. This error usually occurs when using an EC-Zone User Id and Password. Error An error occurred. Approved is set to 'True', so transaction is assumed to be successful Authorize. NET CIM Description I00001 The request was processed successfully. I00003 The record has already been deleted. E00001 An unexpected system error occurred while processing this request. E00003 This is the result of an XML parser error. E00004 The name of the root node of the XML request is the API method being called. It is not valid. E00005 Merchant authentication requires a valid value for transaction key. E00006 Merchant authentication requires a valid value for name. E00008 The payment gateway or user account is not currently active. E00009 The requested API method cannot be executed while the payment gateway account is in Test Mode. E00010 The user does not have permission to call the API. E00011 The user does not have permission to call the API method. E00013 One of the field values is not valid. E00014 One of the required fields was not present. E00015 One of the fields has an invalid length. E00016 The field type is not valid. E00019 The customer tax ID or driver's license information driver's license number, driver's license state, driver's license DOB is required for the subscription. E00027 An approval was not returned for the transaction. E00029 Payment information is required when creating a subscription or payment profile. E00039 A duplicate of the customer profile, customer payment profile, or customer address was already submitted. E00040 The profileID, paymentProfileId, or shippingAddressId for this request is not valid for this merchant. E00041 All of the fields were empty or missing. E00042 The maximum number of payment profiles for the customer profile has been reached. E00043 The maximum number of shipping addresses for the customer profile has been reached. E00044 The payment gateway account is not enabled for Customer Information Manager CIM. E00045 An error exists in the XML namespace. This error is similar to E00003 E00051 If the customer profile ID, payment profile ID, and shipping address ID are included, they must match the original transaction. Barclay: Description 1 Approved. Transaction was declined by the authoriser, but it might receive voice approval. This is also known as a soft decline. Transaction was declined by the authoriser and it is unlikely that it would receive voice approval. This is also known as a hard decline. There is something wrong with the transaction which prevents it from processing. See ErrorText for more information. Beanstream: Description 1 Transaction approved. Bluefin: Description 0 Declined 1 Approved BluePay: Description 0 Declined 1 Approved E Error BrainTree: Description 1 Transaction Approved. Additional response codes for the BrainTree gateway are included below: Description 100 Transaction was approved Approved. Converge: Description 0 APPROVED Transaction approved. See for additional information. Cyber Cash: Description 0 Approved - Anything other than an approved transaction will return no code. However, the field will contain the error message. Cyberbit: Description -1 Incorrect Matching Code. CyberSource: Description ACCEPT Transaction approved. REJECT The request was rejected. Check the for the reason why. ERROR There was a system error. Data Cash: Description 1 Success - Transaction accepted and logged. The argument is e. The argument will give a better indication of what exactly went wrong. The arguments are as return code 1, except the first argument is the bank's reason for declining it e. REFERRAL, CALL AUTH CENTRE, PICK UP CARD etc. FRAUD DECLINED reason code 9 Currency error - The currency you specified does not exist. Diner's Club, American Express if the merchant does not take American Express, Domestic Maestro if multicurrency only. Contact DataCash Technical Support. MoTo, e-comm , but you have not specified from which environment this transaction has taken place. The first digit 2, 9, 3 or 4 indicates the format used and whether the txn was processed in a live or test environment. The number supplied failed to pass the luhn check. Eway: Description True Transaction authorized. Anything else Transaction declined. It is extremely unlikely you will ever see this return code in this context, although you may see it when browsing old transactions in the NetBilling database via the Admin tools. A more detailed message will be available in the field. Other Code Any other non-zero, non-null codes should be interpreted as success for compatibility with future response codes. Returned on API calls which don't involve executing a payment or payment cancellation. Indicates the payment was accepted and successfully issued for authorization. Indicates the request to cancel a payment was received and successfully issued to the processor. Error Indicates an error occurred in processing your request. Any number of problems could produce an error condition. ResponseText will contain the further error details. Declined Indicates that a payment authorization has been denied by the processor. ResponseText may contain further details. Settled Indicates that the transaction was issued for Settlement and was successfully accepted. If a payment action receives a Settlement Error you should contact PayPoint Support personnel for additional details. If you wish to start accepting credit cards contact PayPoint Support personnel. PayPoint enables only cards being accepted by your Payment Processor. This limit is determined at the time you fill out your PayPoint application. The default setting is unlimited. Unless you explicitly request a limitation on your PayPoint application you will never see this return code. This limit is determined at the time you fill out your PayPoint application. The default setting is unlimited. Unless you explicitly request a limitation on your PayPoint application you will never see this return code. This feature is determined at the time you fill out your PayPoint Application. The default setting is set to not check for duplicates. Unless you explicitly request a duplicate payment check option on your PayPoint application you will never see this return code. This process checks to ensure that your request conforms to the specification. For example that you have provide all required data elements in your request, or that you are passing proper data types i. If your request fails this validation process PayPoint will reject your request with this return code. The Result Message will provide more specific details on what data failed validation. Chargeback Indicates that the payment was successfully charged back. You should never see this result code. If this error is ever seen contact PayPoint Support personnel. For example if you have a primary payment and a convenience fee payment under the same transaction and only the primary payment has been issued for settlement. Another possible example is a E-Check payment which is refunded, the original payment would be settled but the refund may not have settled yet. This result code means a payment has been sent off for settlement, but we have not received back confirmation of the settlement result. Settlement results within ACH are typically updated as a result of no negative activity within the first 6 days from the settlement issuance. If you wish to start accepting E-Checks contact PayPoint Support personnel. PayPoint provides fraud detection services. PayPoint provides the ability to enable identity verification services for an additional cost. These services are offered to allow clients to be NACHA compliant with consumer identity requirements. If enabled this result code indicates that the payment is being rejected because you did not provide the required identity data such as Driver's License Number or SSN. PayPoint supports the ability to require the issuance of Pre-Notes for registered accounts. If your application is enabled to require Pre-Notes it may also be set to require a successful pre-note before accepting payments. You will receive this result code for any payments received prior to completion of the pre-note process for a given registered account. PayPoint supports the ability to require the issuance of Pre-Notes for registered accounts. If your application is enabled to require Pre-Notes it may also be set to require a successful pre-note before accepting payments. Indicates that the Pre-Note request for a registered account has failed. No Payments can be applied against the registered account until the account information is updated and a new pre-note is issued by PayPoint. You will receive this result code for any payments received prior to correcting the registration information and successful issuance of the pre-note. Consumers have the right to issue a stop payment up to 60 days after making an original payment. This result code indicates that we received a stop payment request through the ACH network and have reversed the original payment transaction within PayPoint and a reversal has been issued against the merchants account. This indicates that a E-Check which was issued for settlement resulted in a Non-Sufficient Funds return. Depending on your configuration the payment will be re-presented through the ACH network up to 2 additional times. If you see this message it indicates 1 of 2 possible attempts. This indicates that the consumers account has insufficient funds to process the original payment request. As a result PayPoint will reverse the transaction. In addition a reversal of the original payment request will be issued against the merchants account. When a E-Check payment request is received PayPoint will perform a basic check of the account and routing numbers provided against known data sources such as Thomson account files to ensure the account number is valid. However after a payment is issued for settlement there can be other conditions that result in invalidating the use of the account number. One example is consumers who may have debit blocks on their accounts which would result in a denial by the consumers back to allow the debit to take place. If an Invalid account result is received PayPoint will reverse the transaction within PayPoint. In addition a reversal of the original payment request will be issued against the merchants account. PayPoint only support postdated transactions for E-Check payments. Once the payment date is reached the payment request will be sent through the normal payment authorization and settlement processing. This result indicates that at the time the Make A Payment request sent the payment was posted dated beyond the acceptable limits. PayPoint can support postdated payments up to 365 days. The default value is to not accept postdated payments. When you fill out your PayPoint Application form you must identify the number of days your application will accept posted dated payments. Account Verification is a feature that can be enabled on your PayPoint account to make a verification request of the account data associated with the registration data being created or updated. Eligible Result code is specific to PINless debit cards. The result is returned as a result of a call to the PinlessDebitCheck API call. This result code indicates that the card is eligible to be processed through the PINless debit network. The result is returned as a result of a call to the PinlessDebitCheck API call. This result code indicates that the card is NOT eligible to be processed through the PINless debit network. This result is returned when your PayPoint account is not enabled to process PINless debit transactions. This result is returned when your PayPoint account is not enabled to process PIN debit transactions. Global Iris: Description 00 Successful 101 Declined by Issuing Bank 102 Referral by Issuing Bank treat as decline in automated system such as internet 103 Card reported Lost or Stolen 106 AUTH FAILED CONTACT AUTH CENTRE 107 FAILS REALSCORE FRAUD CHECKS 108 USING TEST SYSTEM. PLEASE USE PREAPPROVED TEST CARDS ONLY 109 COMMS ERROR SCHEDULED Issuing BANK MAINTENANCE 200 UNSPECIFIED BANK ERROR 202 NETWORK ERROR: CANNOT CONNECT TO EpoS. Please contact Global Iris. We apologise for the inconvenience. Please contact Global Iris Support Team if you continue to experience this problem. Please contact Global Iris Support Team for further details. Global Payroll: Description 00 Transaction was Approved 01 Error - invalid request. POS Gateway is not sure if the transaction was successful or not. HSBC Description A Approved. Transaction was declined by the authoriser and it is unlikely that it would receive voice approval. This is also known as a hard decline. Transaction was declined by the authoriser, but it might receive voice approval. This is also known as a soft decline. There is something wrong with the transaction which prevents it from processing. Intellipay: Description A Approved. The purchase has been authorized by the issuer. The DTS has detected a possible duplicate transaction. The authorizer has declined the purchase request. The card has expired. A data entry error of some kind has occurred. An unknown processor or issuer error has occurred. A system failure of some kind has occurred. JetPay XML: Description 000 Approved 001 Refer to card issuer. DECLINED the transaction was declined. FRAUD Fraudulent transaction detected. Merchant Partners: Description Declined Transaction declined. CALL Call processor for authorization. DENY transaction denied, permanent denial, not likely to succeed on further attempts. RETRY Temporary error, retrying the transaction may yield a different result. Typically these are clerk-initiated retries, not automated. TIMEOUT Transaction not processed in allocated amount of time. Moneris Canada and USA : Description 0 Declined or incomplete. My Virtual Merchant: Description 0 APPROVED Transaction approved. See for additional information. Netbanx: Description ACCEPTED The transaction was processed. DECLINED The transaction was declined before it was sent for processing. ERROR The transaction was attempted but failed. Network Merchants: Description 1 Accepted 2 Declined 3 Error Ogone: Description 0 Incomplete or invalid 1 Cancelled by client 2 Authorization refused 4 Order stored 41 Waiting client payment 5 Authorized 51 Authorization waiting 52 Authorization not known 55 Stand-by 59 Authoriz. Pay Direct: Description 0 Failed Transaction 1 Successful Transaction for Charge and Settle 2 Voided or Refunded Transaction 5 Pending Credit for First Data 7 Successful Authorization Transaction 9 Pending Transaction 10 Successful Pending E-Check Transaction 21 eCheck NSF 22 eCheck NSF 23 eCheck Return 24 eCheck Return Pay Junction: Description 00 Approved. FE There was a format error with your Trinity Gateway Service API request. AE Address verification failed because address did not match. ZE Address verification failed because zip did not match. XE Address verification failed because zip and address did not match. YE Address verification failed because zip and address did not match. OE Address verification failed because address or zip did not match.. UE Address verification failed because cardholder address unavailable. RE Address verification failed because address verification system is not working. SE Address verification failed because address verification system is unavailable. EE Address verification failed because transaction is not a mail or phone order. GE Address verification failed because international support is unavailable. NL Aborted because of a system error, please try again later. AB Aborted because of an upstream system error, please try again later. Pick up card Special Condition. Pick up card Lost. Pick up card Stolen. N4 Declined because the amount exceeds issuer withdrawal limit. Pay Leap: Description -100 Transaction NOT Processed; Generic Host Error 0 Approved 1 User Authentication Failed 2 Invalid Transaction 3 Invalid Transaction Type 4 Invalid Amount 5 Invalid Merchant Information 7 Field Format Error 8 Not a Transaction Server 9 Invalid Parameter Stream 10 Too Many Line Items 11 Client Timeout Waiting for Response 12 Decline 13 Referral 14 Transaction Type Not Supported In This Version 19 Original Transaction ID Not Found 20 Customer Reference Number Not Found 22 Invalid ABA Number 23 Invalid Account Number 24 Invalid Expiration Date 25 Transaction Type Not Supported by Host 26 Invalid Reference Number 27 Invalid Receipt Information 28 Invalid Check Holder Name 29 Invalid Check Number 30 Check DL Verification Requires DL State 40 Transaction did not connect to NCN because SecureNCIS is not running on the web server 50 Insufficient Funds Available 99 General Error 100 Invalid Transaction Returned from Host 101 Timeout Value too Small or Invalid Time Out Value 102 Processor Not Available 103 Error Reading Response from Host 104 Timeout waiting for Processor Response 105 Credit Error 106 Host Not Available 107 Duplicate Suppression Timeout 108 Void Error 109 Timeout Waiting for Host Response 110 Duplicate Transaction 111 Capture Error 112 Failed AVS Check 113 Cannot Exceed Sales Cap 1000 Generic Host Error 1001 Invalid Login 1002 Insufficient Privilege or Invalid Amount 1003 Invalid Login Blocked 1004 Invalid Login Deactivated 1005 Transaction Type Not Allowed 1006 Unsupported Processor 1007 Invalid Request Message 1008 Invalid Version 1010 Payment Type Not Supported 1011 Error Starting Transaction 1012 Error Finishing Transaction 1013 Error Checking Duplicate 1014 No Records To Settle in the current batch 1015 No Records To Process in the current batch PayFlow Link: Description 0 Approved - Anything other than an approved transaction will return no code. However, the field will contain the error message. PayFlow Pro: Description 0 Approved. Your merchant bank account does not support the following credit card type that was submitted. Transaction type is not appropriate for this transaction. For example, you cannot credit an authorization-only transaction. Processor does not recognize your merchant account information. Contact your bank account acquirer to resolve this problem. Please check the credit card number and transaction information to make sure they were entered correctly. If this does not resolve the problem, have the customer call the credit card issuer to resolve. Transaction was declined but could be approved with a verbal authorization from the bank that issued the card. Submit a manual Voice Authorization transaction and enter the verbal auth code. The transaction ID you entered for this transaction is not valid. Please check credit card number and re-submit. Please check and re-submit. This could be caused by an unrecognized XML tag or a bad XML format that cannot be parsed by the system. Try your transaction again. Please make sure you have not already credited this transaction, or that this transaction ID is for a creditable transaction for example, you cannot credit an authorization. Please make sure the transaction ID entered has not already been voided. If not, then look at the Transaction Detail screen for this transaction to see if it has settled the Batch field will be set to a number greater than zero if the transaction has been settled. If the transaction has already settled your only recourse is a reversal credit a payment or submit a payment for a credit. Only authorization transactions can be captured. Address and zip code do not match. For ACH transactions only not supported. An authorization may still exist on the cardholder's account. An attempt was made to submit a transaction that failed to meet the security settings specified on the VeriSign Manager Security Settings page. See VeriSign Manager User's Guide. This is a generic message returned by your credit card processor. The message itself will contain more information describing the error. PayFuse: Note, this is a selection of error codes. Please see the API docs for a complete list. Only codes 1 and 4 indicate approval. However, it failed a postprocessing fraud rule and has been voided. However, it failed a fraud rule and has been marked for review. It may already be voided or settled. It may be a voided a transaction or an unsettled transaction. It may already be captured or settled. It may already be voided, settled, or an uncaptured authorization. Please retry this transaction again. Please log into virtual terminal to reset password. Payvision: Description 0 There were no errors during the execution of the operation. PayWiser: Description -1 Invalid caller -2 Invalid parameters -3 Duplicate ReferenceID -4 Error calling bank -5 Unknown card type -6 Wrong format of CardExpDate -7 Invalid CheckReferenceID -8 Invalid PGReferenceID -9 Amount is out of bounds either 0 or not between min and max -10 Invalid ReservationReferenceID -11 General processing error -12 Invalid InitPaymentReferenceID -13 Web payment is no longer active -14 Web payment was already processed -15 Invalid PaymentCheckURL response -16 Invalid card region intra -17 Invalid card region inter -18 Hourly transaction count limit exceeded -19 Daily transaction count limit exceeded -20 Monthly transaction count limit exceeded -21 Hourly transaction sum limit exceeded -22 Daily transaction sum limit exceeded -23 Monthly transaction sum limit exceeded -24 Hourly card transaction count limit exceeded -25 Daily card transaction count limit exceeded -26 Monthly card transaction count limit exceeded -27 Invalid WebFormLanguage -28 Invalid TemplateID -29 Invalid RecurringScheduleID -30 General Moneta error -31 Invalid AgreementID -32 Agreement not confirmed -33 3DS error - wrong card type -34 3DS processing error -35 3DS is not set up for this account -36 3DS is not allowed for this account -37 3DS error - parameter ThreeDSecurePaRes or ThreeDSecureReferenceID is required -38 3DS error - parameter ThreeDSecureData is required -39 3DS error - ThreeDSecureReferenceID not found or not completed -40 Maestro cards cannot be tokenized. Unable to process this card for 10 minutes. PaymentAmount instead -58 Recurring ExpiryDate must be after FirstPaymentDate -59 Recurring FirstPaymentDate can not be before today -60 Duplicate RecurringReferenceID -61 Recurring payments are now allowed for this account -62 Recurring schedule does not exist -63 Recurring schedule is already terminated -64 Invalid PlanPattern value -65 Invalid RetryPattern value -66 MaxRetryCount must be greater or equal to 0 -67 Either both MaxRetryCount and RetryPattern or none of them must be specified -68 PaymentHour must be between 0 and 23 -69 Card with specified CardToken does not exist -70 Recurring plan can not have InstallmentTotalValue -71 ImmediatePaymentAmount is out of bounds either 0 or not between min and max -72 PaymentAmount is out of bounds either 0 or not between min and max -73 Card payments are now allowed, specifying AllowCards is not allowed -74 Moneta payments are now allowed, specifying AllowMoneta is not allowed -75 AdjustPlanWithStartDate is not allowed with specified recurring plan pattern -76 RenewYearly is only allowed with installment type not recurring and for monthly plans with less than 12 installments only -77 Sepa payments are now allowed for this account -78 Invalid MandateSignatureDate -79 Duplicate MandateID -80 MandateID does not exist -81 MandateID is already revoked -82 Amount is out of bounds either 0 or not between min and max -83 Invalid CheckPaymentReferenceID -84 Invalid Sepa Sequence -85 Invalid MandateValidFromDate -86 Sepa collection date can not be before current day -87 Sepa payment date is out of bounds either to soon or too late for bank processing, check StartDate -88 Invalid CollectionDate -89 MandateID is allowed only for Sepa payments -90 Sepa mandate is canceled -91 Currency mismatch different currency than used for Reserve -92 Invalid Amount larger than used for Reserve -93 Sepa mandate has already been used -94 Invalid combination of CardToken, SepaMandateID and MonetaAgreementID - only one can be used -95 Recurring payments require recurring mandate -96 One or more itms in the list has Currency different from the payment Currency -97 Either CardToken, SepaCreditorMandateID or MonetaAgreementID must be specified -98 Sepa first payment date is out of bounds either to soon or too late for bank processing -99 Sepa consecutive payment dates are out of bounds either to soon or too late for bank processing -100 Sepa consecutive retry dates are out of bounds either to soon or too late for bank processing -101 Sepa payments are now allowed, specifying AllowSepa is not allowed -102 MonetaDO settings missing -103 MonetaDO error -104 MonetaDO agreement does not exist -105 MonetaDO agreement is not yet confirmed by the customer -106 MonetaDO agreement is canceled -107 MonetaDO reservation does not exist -108 Only EUR currency is allowed for Moneta payments -109 AgreementID is not allowed for non-recurring payments -110 AgreementID is allowed only for moneta payments -111 MobileNumber does not support Moneta payments -113 General Sepa error -114 Invalid characters -115 Sepa error - access token not available -116 Payouts are not allowed for this account -117 Surcharge+Cashback can not be greater than Amount -118 Invalid Surcharge amount larger than used for Reserve -119 Invalid CashBack amount larger than used for Reserve -120 Surcharge is allowed only for card payments -121 Surcharge can not be greater than Amount 0 Ok 305 3DS is needed 1000 Confirmation requested 1001 Agreement not active 20000 Approved 40000 General input error 40110 Invalid card number 40120 Invalid CSC 40130 Invalid expire date 40135 Card expired 40140 Invalid currency 40200 Clearhaus rule violation 40300 3-D Secure problem 40310 3-D Secure authentication failure 40400 Backend problem 40410 Declined by issuer or card scheme 40411 Card restricted 40412 Card lost or stolen 40413 Insufficient funds 40414 Suspected fraud 40415 Amount limit exceeded 50000 Clearhaus error 40000 General input error 40110 Invalid card number 40120 Invalid CSC 40130 Invalid expire date 40135 Card expired 40140 Invalid currency 40200 Clearhaus rule violation 40300 3-D Secure problem PhoeniXGate: Description -100 Transaction NOT Processed; Generic Host Error. R1 STOP RECURRING Customer requested stop of all recurring payments from specific merchant. If any other ARC is returned for a recurring transaction, the schedule is automatically canceled. PlugNPay: Description A Approved. C Call Auth Center. P Pick up card. ProPay XML: Description 00 Success 20 Invalid username 21 Invalid transType 23 Invalid accountType 24 Invalid sourceEmail 25 Invalid firstName 26 Invalid mInitial 27 Invalid lastName 28 Invalid billAddr 29 Invalid aptNum 30 Invalid city 31 Invalid state 32 Invalid billZip 33 Invalid mailAddr 34 Invalid mailApt 35 Invalid mailCity 36 Invalid mailState 37 Invalid mailZip 38 Invalid dayPhone 39 Invalid evenPhone 40 Invalid ssn 41 Invalid dob 42 Invalid recEmail 43 Invalid knownAccount 44 Invalid amount 45 Invalid invNum 46 Invalid rtNum 47 Invalid accntNum 48 Invalid ccNum 49 Invalid expDate 50 Invalid cvv2 51 Invalid transNum or unavailable to act on transNum due to funding 52 Invalid splitNum 53 A ProPay account with this e-mail address already exists or User has no AccountNumber 54 A ProPay account with this social security number already exists 55 The email address provided does not correspond to a ProPay account. This return code should be handled as a success. Details about the original transaction are included whenever a 69 response is returned. These details include a repeat of the authcode, the original AVS response, and the original CVV response. PSIGate: Description APPROVED The card issuing bank approved the transaction request. DECLINED The transaction request was accepted as a valid request and was declined by the card issuing bank. ERROR The transaction request encountered an error. QuickBooks Merchant Services QBMS : Description 0 Status Ok - Request succeeded. If you want to void or cancel it, you must do so manually. Depending on the merchant's fraud settings, QBMS may try to automatically void the transaction. If that fails, as is the case with this status code, you must void or cancel the transaction manually. In this case, even though the auth is rejected, the auth is kept on file against the customer card up to 15-30 days after the rejection. Indicates a communication problem, rather than an error resulting from transaction content. Could not log in to the QBMS processing gateway. Could not validate the QBMS account. For example, some values require integers only, while others require decimals. The maximum length has been exceeded. Unexpected data was found during the validation. This error can occur for various reasons, for example if the value supplied in the TransactionAmount property is not formatted correctly dollars, period, cents to two decimal places , you'll get this error. The TransactionId should be unique within this time window. The attempted transaction exceeded the customer's credit limit on the credit card. For example, the account may have been closed, or activities may have been temporarily stopped for that card due to security reasons. The transaction may have already been settled. The transaction has been captured already, has been voided, has expired, or the capture request has used the incorrect authorization transaction ID. An incorrect format was used for a field value, such as the transaction ID. For example, this error could occur if the card in question has expired between the time of authorization and the time of an attempted capture. A check transaction is being duplicated. Repay Gateway: Description -100 Transaction NOT Processed; Generic Host Error. Sage Payments: Description A Transaction approved. E Front-End Error Not approved X Gateway Error Not approved SagePay: Description OK Process executed without error. The DEFERRED payment was released. MALFORMED Input message was malformed - normally will only occur during development. INVALID Unable to authenticate you or find the transaction, or the data provided is invalid. If the Deferred payment was already released, an INVALID response is returned. ERROR Only returned if there is a problem at Protx. Approval Code available as bank reference N Transaction not authorized. Failure message text available to merchant C Communication problem. Trying again later may well work P:A Pre-bank checks. Amount not supplied or invalid P:X Pre-bank checks. Not all mandatory parameters supplied P:P Pre-bank checks. Same payment presented twice P:S Pre-bank checks. Start date invalid P:E Pre-bank checks. Expiry date invalid P:I Pre-bank checks. Issue number invalid P:C Pre-bank checks. Card number fails LUHN check P:T Pre-bank checks. Card type invalid - i. Customer name not supplied P:M Pre-bank checks. Merchant does not exist or not registered yet P:B Pre-bank checks. Merchant account for card type does not exist P:D Pre-bank checks. Merchant account for this currency does not exist P:V Pre-bank checks. Transaction timed out awaiting a virtual circuit. Merchant may not have enough virtual circuits for the volume of business. Skipjack: Description 0 Transaction is not approved. Authorized The Transaction was processed. Declined The bank declined the transaction. Voided Canceled by user. Canceled Canceled by PRIGate. Usually because provided data is insufficient. Qued Placed in que for later processing. Credit cards usually take 2 hours. ACH 11am next day. UnKnown Unknown transaction status. TransFirst: Description 00 APPROVAL Approved and completed. ERROR Invalid card number. L2 PASSWORD INVALID Password is missing or invalid. L3 EXPIRATION DATE INVALID Expiration Date is not formatted correctly. L6 ORDER NUMBER MISSING The Order Number is required but missing. L7 WRONG TRANSACTION CODE Transaction Code must be either a 30 for Authorize Only, 32 for Authorize and Settle. L8 NETWORK The Network Connection timed out due to a communications error. TransNational Bankcard: Description 1 Transaction approved. Trust Commerce: Description approved Transaction received on-line approval sales, auth-onlys accepted Transaction accepted for later processing credits, captures, etc error Gateway system error baddata Invalid fields sent to gateway. USAePay: Description Approved Transaction approved. Error There is an error in the data received. Verifi: Description 1 Transaction approved. WorldPay Select Junior: Description A Transaction authorized. Anything else Transaction declined. WorldPay US Link: Description Declined Transaction declined. WorldPay XML: Description AUTHORISED Transaction authorized. YKC: Description 1 OK.

transmission data parser failure authorization code is malformed or invalid

Please remove the unused column from the input column list. This field is currently defined to be 0x1. Host ACK mode waits for the DMA of the MTX buffer that contains the data file to complete before sending the ACK. CR121378 In WebLogic Server 7. Please record and report this error to the appropriate administrator. CR209383 POST data is no longer getting chunked when FileCaching is set to OFF. CR108496 When editing an EJB deployment descriptor from the console, the tag was being met to true in the deployed EJB jar file.