What are the Implementation Processes?

It is important to understand the business logic of the implementation processes. We can set up to different processes:


ACQUIRING Workflow – this is set up for direct acquiring service. For implementation of this service follow the documentation for Acquiring service:  https://docs.api.isignthis.com/payment-processing-services-create-transaction/


EMONEY Workflow – this is set up for the pass-through wallet, which is a pre-stage of our wallet. This product includes identity (on first deposit or threshold, depending on the merchant). API docs for Paydentity apply: https://docs.api.isignthis.com/identity-services-create-transaction/ . End user might be required to pass identification and verification while making a deposit. It is important to also implement link to pending transactions for this process. A KYC transaction would typically include a payment and verification such as uploading documents. If the end user stops at that stage, you will need to have a way of returning them to this pending KYC transaction. This can be done by calling the redirect_url returned to you in our response to your original request. Therefore, it is important that you look at the pending notifications too. 


Returning to a Transaction: Returning to a transaction is an important factor when conducting a Paydentity workflow. A customer might not have on hand the documents which are required to complete a KYC process and therefore return later to the transaction when all documents have been gathered. For a customer to be able to return to a transaction and complete the KYC process, the redirect url from the API Request Response must be stored by the merchant and be accessible by the customer later on. A transaction is pending unless you receive a final notification as per: https://docs.api.isignthis.com/events/