Here’s the process to follow to build a provider implementation for a service
...
Core service description: Now, identify the service you want to implement. Thoroughly read and understand it’s service description. If it doesn’t exist for the service you are thinking of implementing, contact Hussein Alayo or Victor Irechukwu to write it up. Don’t continue till this is done.
Understand and document the pricing: See to it that a section has been added to https://docs.google.com/spreadsheets/d/1UyAXwtarMBj0glpvT7wWuoIUpyIHCVy1ED7fdbUicRQ/edit#gid=249347743 for the provider and all pricing details filled for the service(s). Then set the API mappings column as well. Don’t continue till this is done.
Test Provider APIs: Create a collection of the provider’s APIs, test them against their test environment and get responses for every endpoint. Save this responses and create mocks. Save the final functional collection in the Provider APIs workspace on the OnePipe Postman account.
...
Settlement and fees model
Process flows and sequence of API calls
Any special notes.
List out what needs to be configured in provider override settings
...
Don’t continue till this is done.
Review the design: Review this design with at least 2 people. Discuss the settlement modalities with Victor Irechukwu and Yvonne-Faith Elaigwu to ensure it works out.
...