Currently with NAB Transact we conduct what is called a Direct Post and a browser redirect when a transaction takes place.
This is so that Synergetic does not handle sensitive information, such as credit card numbersm, thus enabling us to be PCI compliant.
Current approach
Following the Direct Post the user is redirected back to a Synergetic URL to continue working within the Synergetic web application.
However, in rare case, there may be a client issue where the session is unexpectedly closed.
This may cause the redirect not to happen, and as a result the corresponding information about the reciept is not stored in the Synergetic base tables meaning that the payment can not be automatically reconciled.
The current resolution in this case is to this is to create a manual receipt for the payment.
New approach
We are introducing a complementary process that will have NAB Transact initiate a callback in addition to the redirect process.
This callback will happen regardless of the client session state or existance.
This effectively creates a redundancy in the communication back to Synergetic, ensuring that Synergetic is aware of the success or failure of the transaction.
Synergetic Core API will need to be publically accessible.
Q&A
Q. Will this create duplicate records in the receipts tables?
A. No.