Appendix 2 - Authorization flow explanation

Previous   |  Direct link to this topic

iPayment only starts the authorization/settle process after the document has been added. This way we can be sure the data is in the database and that we authorize on the correct document and that nothing else is blocking the sales order from getting added (Like a stored procedure). We do it this way to avoid the scenario where the authorization is added to the gateway, the sales order add is blocked by the transaction notification/another add-on and the user then decides to not add the sales order. In this scenario we would end up with an authorization that would not be linked to any document.