|
Direct Payment Integrator V6
Questions / Feedback?
FDMSSettleResponse Type
Contains the response to the batch settlement..
Remarks
This type contains the results of a transaction made with the FDMSSettle component. The fields contained by this
type are listed below.
Fields
| |
BatchNumber String |
FDMS-generated Id of the batch settlement.
This field is filled after a successful batch settlement, and contains a unique number which
identifies the settlement with the FDMS processor. This number should be logged in case you have
any questions about the settlement in the future.
|
BatchStatus String |
Indicates success or failure of the entire settlement.
This field will be filled after calling the SendSettlement method. If it contains "OK", the batch settlement
has succeeded. If it contains any other data, an error will be generated by the component. Possible responses include:
| | Code | Description | OK | Batch completed successfully. | DUP GEN RECORD | Duplicate general record. | DUP RECORD | Duplicate detail record. | INVLD ACCT 1 | Merchant attempted to capture a transaction for which he is not entitled. | INVLD ACCT 2 | Merchant entered an invalid account number (length or prefix error). | INVLD AMT 3 | Merchant entered an invalid amount in the capture transaction. | INVLD FIELD DATA | Invalid field data. | INVLD GENERAL TYPE | Invalid or duplicate header record. | INVLD LENGTH | Invalid length when extracting ISO field from data buffer. | INVLD RECORD TYPE | Unknown record type. | INVLD SETTLE 4 | The item count or dollar total does not agree. Correct and retransmit the entire batch. | INVLD SETTLE 5 | System rejected batch for reasons unrelated to a specific record. | INVLD SUPPL DATA | Invalid supplemental data. | INVLD TRANS CODE | Invalid trans code. | NO HEADER RECORD | No header record. | PLEASE RETRY | Server has timed out. Please retry batch. | SUPPL OUT OF SEQ | Supplemental batch sequence number does not match original. | TCH OUT OF SEQ | Batch sequence number does not match count. | UNSUPPORTED TRAN | Batch Review (Tran Code 97) not supported. | INV SETTL TR1 | Batch rejected for invalid track 1 data | INV SETTL TR2 | Batch rejected for invalid track 2 data | INVLD DATA! | Data format does not correspond to fields identified in the bit map. | (any other data) | Consider request not approved. |
|
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:
| | OK | Transaction has successfully passed through the Datawire system to the FDMS Payment processor and back. | AuthenticationError | DatawireId in the request was not successfully authenticated. | UnknownServiceID | ServiceId part of the URL (in the Service Discovery or Ping request) is unknown. | WrongSessionContext | The SessionContext element of the Session Transaction request does not match the
SessionContext returned by the InitiateSession response (applicable to the FDMSSettle component). | AccessDenied | Generally, occurs when you try to register a merchant after a merchant has already been activated to use the Datawire VXN. | Failed | Your Merchant Registration has failed. Contact tech.support@datawire.net for more information. | Retry | Registration is not yet complete. You must send the Registration request again. | Timeout | No response from the Service Provider was received during the expected period of time. | XMLError | Request contains some XML error, such as malformed XML, violation of this DTD, etc. | OtherError | Unspecified error occurred. | 008 | Network Error |
|
Constructors
[VB.NET]
Public FDMSSettleResponse()
[C#]
public FDMSSettleResponse();
|