Go-live checklist
Use this checklist to confirm your integration is ready for production. It brings together the backend work, SDK work, and operational setup that a P2P SDK integration needs, plus the teams you'll want involved along the way.
Before you begin
Before you start, make sure you have the following in place:
- A working Sandbox integration. If you haven't sent a transfer yet, start with Your first sandbox transfer.
- Your test cases passing in the test case simulator.
Backend
- Store your PayMitto API credentials securely on your backend. See Securely storing API credentials.
- Get an access token, and request a new one before it expires. See Your backend's responsibilities.
- Get sender fields and create a sender for each account holder, then save the
senderId. See Create senders. - Confirm funds are available and debit them before you call Create Transfer. See Posting a transfer.
- Handle a
504 Gateway Timeouton Create Transfer by checking transfer progress before you retry. See Error handling. - Consume transfer status updates, and trigger refunds from the status event.
SDK
- Add the SDK for each surface you're launching: the Web SDK, a native SDK for iOS, Android, or React Native, or both.
- Handle the authentication callback, so the SDK gets the token it needs. For the Web SDK, see Web SDK authentication.
- Handle the transfer callback, and report the result back to the SDK.
Account holder experience
- Show a receipt and meet disclosure requirements. See SDK receipt compliance.
- Send a transfer confirmation email.
- Plan account holder messaging for a transfer that stays Pending while screening completes.
Operations
- Set up single sign-on for your staff to the PayMitto Admin Portal. See SSO setup.
- Receive and reconcile the daily reports delivered over SFTP. See Reporting and data feeds.
Certification and production
- Complete the certification test cases. See Certification.
- Receive your production credentials, which PayMitto issues after certification.
- Have your backend's production IP addresses allowlisted. See Environments.
Who to involve
Treat this as a checklist for who to invite, not a staffing plan.
| Function | What they own | When |
|---|---|---|
| Backend engineering | Transfer initiation, balance validation, status updates, refunds | Throughout |
| Frontend and mobile | SDK initialization; native iOS and Android if in scope | Build, plus app releases |
| Core banking | Real-time balance access, debit and credit posting, ledger treatment | Early |
| Integration and file transport | SFTP setup, reconciliation file ingestion | Mid-project |
| Identity and access management | Admin Portal single sign-on | Before launch |
| Compliance and legal | Screening outcomes, transaction monitoring, disclosures, Regulation E | From scoping |
| Treasury and finance | Funding structure, reconciliation, FX and fee treatment | Early and ongoing |
| Operations and support | Servicing processes, staff training, documentation | Before launch |
| Quality assurance | Corridor testing, asynchronous status and failure paths | Build and pre-launch |
Next steps
Once you've finished here, these pages are good places to go next:
- Certification: run the certification test cases with PayMitto.
- Reporting and data feeds: what you receive once you're live.
Updated about 13 hours ago
Did this page help you?