4D Payments SDK 2016 .NET Edition
4D Payments SDK 2016 .NET Edition
Questions / Feedback?

FDMSDebitResponse Type

Contains the response to the debit card transaction..

Remarks

This type contains the results of a transaction made with the FDMSDebit component. The fields contained by this type are listed below.

Fields

ApprovalCode
String

Contains an authorization code when a transaction has been approved, or an error message if declined.

This field contains an authorization code when a transaction has been approved. The code will begin with "AP" and will be 8 characters in length. If the transaction was declined, it will contain one of the response messages listed in the table below:

Response MessageMeaning
AMT EXCEED LIMIT Amount exceeds withdrawal limit.
CRYPTO BOX UNAV CRYPTO Box is off-line.
DBT SWITCH UNAVL Communications link to Debit network gateway is down or responded with a "System Malfunction (96)" message.
DBT T.O. RETRY Request was switched but no reply from Debit network gateway within the time-out period.
DBTSW INV MERID EDS says that Merchant ID/SE is invalid.
DBTSW PIN XL ERR EDS has problem in decrypting our cryptogram. (PIN XLATE ERR means FDMS-RACAL6000 has problem decrypting terminal cryptogram. (This remains unchanged.)
DEBIT INV TRK-II Track II data was missing or invalid.
DECLINED Decline the transaction.
DUPLICATE TRAN Receipt/Account number duplicates. Must be unique.
ENTER LESSER Re-enter using a lower amount.
ENTER LESSER AMT Re-enter using a lower amount.
INCORRECT PIN PIN value incorrect.
INV ACCT Invalid card number.
INV ACCT NUM Invalid card number.
INV AMT Invalid amount.
INV CASHBACK AMT Cash-back amount more than total amount.
INV DRIVER NBR Invalid Driver number.
INVALID ID NBR Invalid ID used.
INV VEHICLE NBR Invalid Vehicle number.
INV TRAN Transaction not permitted/allowed to cardholder.
ISSUER UNAV Debit network gateway cannot get through to the issuer.
PIN RETRY EXCEED PIN was entered incorrectly four times (limit).
PIN XLATE ERROR PIN could not be decrypted. If new problem with existing setup, replace PIN pad. Confirm proper key setup for new PIN pads. Confirm proper host setup for new Base Derivation keys.
PLEASE RETRY Generic system error. Please try again.
RESUB EXCDS LMT Resubmission of transaction violates Debit network frequency.
REV REJECTED Reversal was rejected.
TRAN CT EXCD LMT Debit transaction count exceeds pre-determined limit in specified time.
TRAN NOT ALLOWED Transaction not allowed.
UNDEFINED CARD Debit network gateway cannot route card based on Merchant Entitlement.

AuthorizedAmount
String

When supporting partial authorizations, this is the amount actually charged to the debit card.

This is only used when supporting partial authorizations. If the ApprovalCode begins with "AL" this field will contain the amount actually charged to the debit card. This will be less than the original TransactionAmount. You must collect the remainder via another form of payment, or Reverse the authorization if the customer does not have an additional form of payment.

CaptureFlag
Boolean

Indicates whether the authorization was successful, and whether it can be settled.

After an authorization request, the CaptureFlag will be set to True if the request was successfully processed. This indicates that you may send the transaction on for batch settlement using the FDMSSettle component. If this field is False you should consider the transaction as Declined, and it may not be settled.

DatawireReturnCode
String

Contains an error code providing more details about the DatawireStatus received.

When a transaction is successfully passed from the application, through the Datawire system to the FDMS payment processor and back, the DatawireStatus will be "OK" and the DatawireReturnCode will be "000". These two fields have NO BEARING on the actual results of any transaction. Even though the transaction has successfully passed through the Datawire system, it can still fail to be processed successfully by FDMS. This field only indicates that the request reached FDMS, and that FDMS responded with some data.

The CaptureFlag and ApprovalCode fields contain the actual transaction result that was returned by FDMS.

The following is a list of possible Datawire return codes:

000 Transaction successfully passed through the Datawire system to the FDMS Payment Processor and back.
200 Host Busy - The processor's Host is busy and is currently unable to service this request.
201 Host Unavailable - The processor's Host is currently unavailable. For example, the server is sending NAK.
202 Host Connect Error - Could not connect to the processor's Host.
203 Host Drop - The processor's Host disconnected during the transaction before sending a response.
204 Host Comm Error - An error was encountered while communicating with the processor's Host.
205 No Response - No response from the processor's Host
206 Host Send Error - An error has encountered when sending the request to the processor, and the Host daemon cannot continue sending packets to the processor because the connection is broken.
405 Vxn Timeout - The request could not be processed.
505 Network Error - The request could not be processed.

DatawireStatus
String

Status of the communication with Datawire.

When a transaction is successfully passed from the application, through the Datawire system to the FDMS payment processor and back, the DatawireStatus will be "OK" and the DatawireReturnCode will be "000". These two fields have NO BEARING on the actual results of any transaction. Even though the transaction has successfully passed through the Datawire system, it can still fail to be processed successfully by FDMS. This field only indicates that the request reached FDMS, and that FDMS responded with some data.

The CaptureFlag and ApprovalCode fields contains the actual FDMS Transaction Result that was returned.

The following is a list of possible Datawire response status codes:

OKTransaction has successfully passed through the Datawire system to the FDMS Payment processor and back.
AuthenticationErrorDatawireId in the request was not successfully authenticated.
UnknownServiceIDServiceId part of the URL (in the Service Discovery or Ping request) is unknown.
WrongSessionContextThe SessionContext element of the Session Transaction request does not match the SessionContext returned by the InitiateSession response (applicable to the FDMSSettle component).
AccessDeniedGenerally, occurs when you try to register a merchant after a merchant has already been activated to use the Datawire VXN.
FailedYour Merchant Registration has failed. Contact tech.support@datawire.net for more information.
RetryRegistration is not yet complete. You must send the Registration request again.
TimeoutNo response from the Service Provider was received during the expected period of time.
XMLErrorRequest contains some XML error, such as malformed XML, violation of this DTD, etc.
OtherError Unspecified error occurred.
008Network Error

DebitNetworkId
String

Contains the Debit Network ID.

This field contains the Debit Network ID which is used for settlement purposes.

TransactionDate
String

Local transaction date returned from the server in MMDDYY format.

This six digit field contains a local transaction date calculated by the authorization center. This field should be recorded and submitted in the Batch Settlement.

Constructors

[VB.NET]
Public FDMSDebitResponse()

[C#]
public FDMSDebitResponse();



 
 
Copyright (c) 2020 4D Payments Inc. - All rights reserved.
4D Payments SDK 2016 .NET Edition - Version 16.0 [Build 7395]