Integration Checklist
1. Read the Prologue
Actors: Integrator
Every integrator needs to have a high level overview of PAPE, and what it means to be an Integrator, and what the ideal integration team would look like.
Refer to the PAPE overview documentation for more details.
2. Make available an account verification endpoint
Actors: Integrator’s backend team.
Every integrator needs to deploy an account verification endpoint for name checks and AML/transaction verifications.
Refer to the PAPE Account Verification Endpoint documentation for more details.
3. Get Onboarded
Actors: Integrator, Interswitch
The Integrator should provide Interswitch all necessary information to get registered as a payment gateway on PAPE.
Refer to the onboarding documentation for more details.
4. Go through all the tutorials
Actors: Integrator backend team.
The tutorials are geared specifically for the Integrator backend team. Backend engineers need to fully comprehend what is possible on the PAPE platform to advise the frontend guys on possibilities of the PAPE platform.
5. Liquidity Provider Banking Frontend
Actors: Integrator frontend team.
PAPE already provides a full-fledged liquidity provider dashboard, for liquidity providers to setup their exchange rates and initiate withdrawals.
However, liquidity providers cannot deposit funds into their PAPE account within the PAPE provided UI. Deposit of funds has to go through a bank provided frontend.
The frontend teams will have to come up with UIs for liquidity providers to deposit funds to the PAPE platform. This could be an extra menu option inside the currently being used banking software within the bank.
The bank’s frontend and backend teams would also have to agree on authentication, and other security measures (e.g. AML)
6. Banking Customer Crossborder Payment Frontend
Actors: Integrator frontend team.
Banking customers do not interact directly with PAPE for crossborder payments. They interact with frontends provided by the bank itself.
The frontend teams will have to come up with UIs for banking customers to perform cross-border payments within their existing banking apps. This could be an extra menu option or two inside the currently being used banking app.
The bank’s frontend and backend teams would also have to agree on authentication, and other security measures (e.g. AML)
7. Plan a Proof of Concept
Actors: Interswitch, Integrator.
A proper proof of concept will need the following:
At least two financial institutions. If you’re a financial institution in multiple countries, each country could serve as a payment gateway. If you’re a financial institution in only one country, Interswitch may provide another payment gateway to work with.
At least one liquidity provider that has been onboarded by your financial institution. Note that the bank itself initially could serve as its own liquidity provider between itself and other financial institutions, while waiting to recruit other accredited liquidity providers.
Agreement on fees for honoring cross-border payments. High level management within the bank will need to agree on cross-border payment fees . Interswitch will update the current Fee Structure for your payment gateway.
8. Deploy PAPE service.
Actors: Integrator’s backend, frontend, and devops teams
Deployment is done by the integrator on their own servers.
9. Test
Actors: Integrator’s backend, frontend, and devops teams
- Test deposits and withdrawals for liquidity providers.
- Test crossborder payments for bank customers.