Implementation overview

This page lays out the technical phases of a PayMitto integration, from receiving Sandbox credentials to going live, and the teams usually involved in each. Use it to plan your build and to see where each guide fits. The phases run in order, and each one builds on the last.

flowchart LR
  A[Credentials and sandbox] --> B[Server setup]
  B --> C[SDK embed]
  C --> D[Testing and certification]
  D --> E[Go-live]

Phases

PhaseWhat happensTechnical roles
Credentials and sandboxYou receive Sandbox API credentials and Admin Portal access. See Environments.IT or integration lead; Admin Portal admins.
Backend setupYour backend handles credentials, authentication, senders, and transfers. See Your backend's responsibilities.Backend developers.
SDK embedYou embed the Web SDK, a native SDK, or both.Frontend or mobile developers.
Testing and certificationYou run the test cases and complete certification.Developers and QA.
Go-liveYou receive Production credentials, allowlist your backend IPs, and release.IT, DevOps, and integration lead.

IT effort by path

How much of this your team builds depends on your integration path.

  • You own your frontend. Your team builds the backend integration and embeds the Web SDK, a native SDK for your mobile app, or both.
  • You use a digital banking platform. PayMitto's digital banking platform integrations use the Web SDK, delivered as an iframe inside the platform's online banking experience, so most of the work is configuration with your platform provider and PayMitto. See Digital banking platforms.

Timelines vary by integration path, so confirm yours with the PayMitto Integrations Team as you plan.

Next steps

Once you've finished here, these pages are good places to go next:


Did this page help you?