Understanding Transaction Statuses

How order are processed in Wyre and what the states reflect.

Once you're live, Wyre will either provide API endpoints for you to track your users transactions or we can supply a full featured Dashboard for a monthly fee (Currently Free!). You'll see a handful of different states in the status such as PRE_AUTH, RUNNING_CHECKS, PROCESSING, FAILED, and our favorite, COMPLETE. These statuses represent different stages of the transaction as the user progresses through the purchase flow.

Currently, debit cards are being pre-authorized before a FAILED or COMPLETE status is returned resulting in a charge to be pending on the users bank statement. If the transaction returns as FAILED the pending transaction will drop off and the user will not be charged. We are working on updating this flow for a better experience.

We've provided a list of common failure reason in the next document "Wallet Order Errors and Exceptions (Failure Reasons)"

Status	Description
PRE_AUTH	PRE_AUTH proceeds all statuses. A user enters the PRE_AUTH stage when they are taken to the card detail page to enter their payment information. If a user does not continue with the transaction they will stay in the PRE_AUTH status.
RUNNING_CHECKS	Once a user has entered their payment information and continued the status will enter the RUNNING_CHECKS state. In this state we are processing the request and seeing if the customer is eligible to transact. If the checks fail the order will immediately transition to FAILED. If the checks pass the order will transition to PROCESSING.
PROCESSING	Orders in the PROCESSING state have passed the checks and the user's payment information has been validated. At this point a Transfer has been created on Wyre for the user's Order. Orders in this state will have the transferId field populated and more status information can be pulled from the Track Widget Order API.
FAILED	Orders in the FAILED state have failed and cannot be processed. If we had additional information on why the order failed we provide it.
COMPLETE	Orders in the COMPLETE state are complete and the funds have been confirmed on the blockchain.

More on PROCESSNG

When an order enters PROCESSING that means that a Transfer has been created that represents the fulfillment of the Order.

While it is not a requirement that you monitor the details of the state in PROCESSING it can make for a better user experience. For example, you could tell the user their funds are on the way before the funds are fully confirmed on the blockchain.

If you wish to track the Transfer to provide additional context to the user we provide an unauthenticated endpoint that can be called directly from your UI. The details of that endpoint can be found on Track Widget Order.

In the case of Orders, funds have already been secured before the Transfer is created. That means that there is really just one thing you need to worry about for the Transfer: when the funds are processed on the blockchain.

There are 3 different states here:

• Blockchain Tx has not been submitted to the network - in this state the Transfer Tracker's blockchainNetworkTx object will appear as null

• Blockchain Tx has been submitted to the network, but has not been confirmed -in this state the Transfer Tracker's blockchainNetworkTx object will be present

• Blockchain Tx has been confirmed - Transfer Tracker will appear as with a COMPLETE status