The Money Transfer Retailer Interface is an HTTP based protocol. A detailed description of the supported operations and definitions can be found in the Specification section.
Throughout the Money Transfer Retailer Interface documentation various terms are used to describe the different entities which send or receive various requests. These terms are described in more detail in this section.
Upstream And Downstream Entities
Upstream and downstream impart a convention for the direction for a request and its response. A request message (such as a request to create a money transfer order) typically originates at a merchant location and must be sent to the money transfer service provider to create the order. When a message is sent from a merchant to a service provider it is said to be sent upstream. Conversely, when a message is sent from a service provider to a merchant it is said to be sent downstream. Thus, ‘upstream entity’ is a relative term and is any entity located between the entity under discussion and the service provider (including the service provider itself). Likewise, ‘downstream entity’ is also a relative term and is any entity located between the entity under discussion and the merchant (including the merchant itself).
Server vs Client
Servers typically host an application and, in the context of the RESTful Money Transfer Retailer Interface, a server would host the money transfer service application responsible for servicing requests received from downstream entities and providing a response. A server is the entity which receives requests and returns responses. A client therefore is the entity responsible for sending requests to a server and expects responses from the server.
The various request and response messages defined in the Money Transfer Retailer Interface are always initiated from the downstream entities and sent to upstream entities for processing. This means that clients are therefore downstream of servers and that servers are upstream of clients. Consider an entity which receives a request from a downstream entity and forwards it to an upstream entity; this entity receives the request in the capacity of a server and passes it on in the capacity of a client.
All communication shall be secured by establishing an SSL encrypted transport. SSL provides a manner for client and server systems to identify themselves to each other as well as to establish an encrypted channel over which they may securely communicate. SSL provides security at a network level and identifies entities who communicate to each other.
Since the Money Transfer Retailer Interface is a RESTful service, server implementations are typically hosted on web servers. Using the HTTP Basic Authentication headers over and above SSL allows the sender of a message to be identified at an application level and any appropriate processing to take place on a per-sender basis.
The failure outcome of a request shall be determined in the first instance by examining the HTTP status code of the response. The HTTP status types and their associated meanings convey information about the possible reasons for a failure response. Where possible, a failure response will also contain further information about the nature of the failure in an ErrorDetail object.
Three basic types of outcomes are possible for transactions, namely: successful, unknown, and failed. HTTP status types are mapped to one of the possible outcomes as indicated below.
|HTTP Status Codes||Status type|
|200, 201, 202, 404*||successful|
|500, 504, timeout||unknown|
|400, 404*, 501, 503, all others||failed|
A timeout occurs when the client has not received a response to a request after an agreed upon interval. Unless otherwise agreed, this interval shall be 60 seconds. Any response received after the timeout should be logged but ignored.
*Note that an HTTP status type of 404 could indicate either a success or a failure; this is dependent on the context of the response. This is covered in more detail in the section on Transaction Flows
In addition to the HTTP status code, failure response bodies shall contain an ErrorDetail object if possible to describe the failure in more detail. It should be noted though that responses in some scenarios which are not successful may contain an empty response body and therefore no ErrorDetail object will be present.
To ensure that loss of transactional data is minimized, it is required that clients store advice messages (see Transaction flows) in persistent storage and queue them for delivery until a final status type is received. A final response is one of either the successful or failed status types. If no response is received, or a response with an unknown status type is received, advice messages shall be queued and the message at the head of queue repeated on an interval until a final status type is received. For high throughput systems it shall be acceptable to send several advice messages in parallel, and as such, advices may be received out of order at the server.