Transaction.migrate call, this object describes a specific validation issue with a submitted transaction.
| Data Members | Data Type | Description |
|---|---|---|
code | string | Required. A numerical code indicating the type of issue that was encountered. Specific codes are listed below. |
description | string | Required. A human readable description of the issue encountered. |
merchantTransactionId | string | Required. Your unique ID for the submitted transaction. |
| Return Code | Description |
|---|---|
200 | The call succeeded. |
400 | Your call failed, which could be due to an authentication failure or a Subscribe failure to find any objects that match your input. 400 may also be one of the following: - Billing has already been attempted for Transaction ID *merchantTransactionId*. - Failed to deserialize Transaction. - Invalid Arguments - No transaction object. |
403 | The Vindicia server cannot authenticate your request. |
404 | One of the following: - Unable to load transaction: no match for merchantTransactionId*merchantTransactionId*. - Unable to load transaction: no match for VID *vid*. |
405 | Unable to save transaction. |
500 | The Vindicia server encountered an internal error. That error could occur for various reasons, the most common being an incorrectly populated input object, especially when you are making the call from a client library whose language does not support strict data-type checking. For resolution, especially during the development phase, contact Vindicia Technical Support. |
503 | A Vindicia back-end service, such as a database, is unavailable. Retry your call later. |
| Parent topic:Transaction Subobjects |