PayMitto P2P is an embeddable SDK for domestic and cross-border person-to-person payments. You embed the Web SDK in your web experience, a native SDK in your mobile app, or both, and connect them to a small backend integration that handles authentication, senders, and transfer submission. These guides walk you through each piece in the order most teams build it, from your first API call to go-live. New to the terms? See the Glossary.

Start by finding the path that matches how your account holders bank with you, then use the section list below to jump to the step you're working on.

PayMitto solutions

PayMitto offers four solutions:

• P2P via the SDK. Domestic and cross-border person-to-person payments, built with the Web SDK and, if you have a mobile app, a native SDK. Most of these guides cover this solution.
• Real Time Account Funding (RTAF). Lets account holders fund a new account in real time from an external card. RTAF uses an Account Funding Transaction (AFT) and is designed specifically for new account funding. The SDK opens directly to the funding screen, and your backend calls the account funding endpoint instead of submitting a transfer. See Real Time Account Funding (RTAF).
• PayMitto Business. Business-to-business (B2B) and business-to-consumer (B2C) payments. See Business payments.
• B2C Disbursements. Payouts from a business to consumers. B2C Disbursements has its own developer documentation.

PayMitto's payout network includes Visa, Mastercard, and MoneyGram, with payouts to bank accounts, debit cards, mobile wallets, cash pickup, and fiat to wallet (stablecoin).

What the SDK handles for you

• Recipient and recipient account collection, including the fields each corridor requires.
• Validation as the account holder types, such as IBAN check digits, with clear prompts to fix mistakes.
• Quotes, exchange rates, fees, and delivery times, shown before the account holder confirms.
• Required disclosures before payment and the receipt after each transfer.
• Localization, light and dark appearance, and your theme and branding.
• Transfer history and status for the account holder.

What your backend handles

• Storing your API credentials and requesting access tokens.
• Creating a sender for each account holder.
• Securing funds and submitting each transfer.
• Receiving transfer status updates.

Which P2P path is right for you?

• You own your frontend. Your team embeds the Web SDK in your web experience, a native SDK in your mobile app, or both. Native SDKs are available for iOS, Android, or the React Native wrapper. Use the Web SDK, a native SDK, or both, depending on where your account holders bank.
• You use a digital banking platform. The PayMitto experience runs inside your platform, and these integrations have used the Web SDK, delivered as an iframe inside the platform's online banking experience. See Digital banking platforms.

Not sure yet? Choose your integration walks through the decision, and the PayMitto Integrations Team is always happy to help at [email protected].

How the docs are organized

The guides follow the order most teams build in:

1. Get started: Choose your integration, see how a PayMitto SDK integration works, and review the implementation overview, roles and responsibilities, and security and trust.
2. Solutions: P2P, RTAF with account funding, and PayMitto Business.
3. Backend setup: Your backend's responsibilities: credentials, authentication, senders, and transfers.
4. Reports and data feeds: Reporting and data feeds, delivered by SFTP.
5. Web SDK: Embed the Web SDK and set up authentication.
6. Native SDKs: Android, iOS, and React Native.
7. Events and webhooks: Transfer status updates.
8. Testing and go-live: Test case simulation, certification, and receipt compliance.
9. Admin Portal: Look up transfers and senders and manage access.
10. Go-live: Certification, receipt compliance, and reporting and data feeds.