Transaction Lifecyle / Workflow
Last updated
PayShield - Transaction Processing / TxProcess
Last updated
Customer completes a purchase on merchant site.
Merchant sends all required purchase data to TxProcess
TxProcess processes the purchase and sends a payment request to the Customers Issuing Bank
The Issuing Bank sends back whether the payment was successful or not.
TxProcess returns the completed payment details to the merchant's system.
Synchronous Transactions are instant payment transactions where the whole transaction life cycle is completed in one call. They are typically associated with credit card transactions such as Visa / Mastercard / CUP / JCB.
Synchronous payments are typically associated with the PAYMENT transaction type. VOID and REFUND are also synchronous calls.
Customer completes a purchase on merchant site.
Merchant sends all required purchase data to TxProcess
TxProcess processes the purchase and sends a payment request to the Customers Issuing Bank
The Issuing Bank sends back an acknowledgment that they have received the payment request. This does not indicate if payment is successful. Just that they have received the request.
TxProcess returns whether the bank has acknowledged the payment request.
The Issuing Bank sends a notification that the payment is now complete and whether it was successful or not.
TxProcess processed the payment notification and sends a notification to the merchant's system that payment is now complete, and whether it was successful or not.
Asynchronous transactions are more complex than synchronous transactions integrations but offer a lot more flexibility and integration types.
Common use cases are for Bank / Wire transfers where a transaction Id is generated and the customer has to manually transfer the money with that transaction Id as a reference, or go to a physical payments office to complete the payment.
When the payment has been confirmed, the Issuing Bank / Payment processor can automatically trigger a call at step 6 confirming payment is complete. In the case of a local Bank Transfer, you may even need to manually acknowledge the settlement in the TxProcess system and mark the transaction as complete, and TxProcess will complete step 7.
Customer completes a purchase on merchant site.
Merchant sends all required purchase data to TxProcess via either a form submit, or a form redirect. Sending the user's browser to the TxProcess server.
TxProcess processes the purchase data and forwards the user's browser to the Intermediary Hosted Form. This could be a different payment processors' hosted form allowing the user to enter credit card details, or an online wallet system that requires the user to validate the purchase request by logging in and confirming payment.
If required, after submitting the intermediary form the payment will be sent to the issuing bank.
The issuing bank will send back the status of the payment request. To the Intermediary
The Intermediary will forward the status of the payment to TxProcess
TxProcess will return the status of the payment, along with the browsers window, to the Merchants system.
The redirect workflow requires that the user's browser window is redirected to the TxProcess server, and will be redirected again to some intermediate form before the transaction is complete. Redirect transactions can either by Synchronous or Asynchronous in nature. Meaning that you could have the final transaction status at the completion of the redirect flow, or you could be waiting for a SETTLEMENT/CAPTURE to come in later. It will depend on the type of integration and payment methods being used.
Common use cases for the Redirect workflow can be for using third-party wallets, where the user has an online balance that they wish to use to complete payment. Redirecting the user to another payment provider online payment form etc.
