   |
|
To gain a basic understanding of EFSnet Web Payment Services, follow a credit card authorization request
as it makes its way through the system.
|
- From a POS terminal, wireless device, PC, Web server, or any equipment that communicates via HTTPS, a merchant sends a transaction
request message to the EFSnet Web service using any one of the three available interface types: SOAP, XML, or CGI (name-value pair).
- EFSnet authenticates the merchant, based on StoreID and StoreKey parameters contained in the request.
- SOAP, XML, or name-value pair transaction request message is converted to the native message format accepted by the processing network.
- Converted transaction request message is sent to the appropriate processing platform.
- The processor sends the authorization request to the appropriate card association based on card type.
- Card association sends the request to the card-issuing bank (financial institution that issued the card).
- Card issuer authorizes or declines the transaction request, sending the response back to the card association.
- Card association sends the transaction response back to the processor, which in turn, passes it back to EFSnet.
- EFSnet converts the message back to a SOAP, XML, or name-value pair response and sends the response back to the merchant.
- Merchant's terminal or application parses the response and displays, logs, and/or prints a receipt depending on merchant needs.
- The entire authorization process occurs within 2-3 seconds.
|
|
Welcome
Flow Diagram