This page splits a PayMitto SDK integration into areas and shows what your systems need to do in each one, alongside what PayMitto and the SDK handle. Use it to scope your build and assign work across your backend, frontend, and operations teams. Each row links to the guide with the details.

Integration responsibilities

The table follows a transfer roughly in order, from authentication through error handling.

Area	Your systems	PayMitto (API and SDK)
Authentication	Store your API credentials on your backend, request access tokens, and give the SDK the token it needs to launch (for the Web SDK, a single-use SLA token). See Securely storing API credentials and Web SDK authentication.	Issues access tokens.
Sender data	Get the required sender fields, collect the data from your records, create the Sender, and save the `senderId`. See Create senders.	Returns the required fields for each sender and stores the Sender record.
Recipients and quotes	Launch the SDK.	The SDK collects recipients and recipient accounts and shows the quote.
Funds movement	Secure (debit) the funds from the sender's account before you submit the transfer.	Delivers the transfer after it is submitted.
Transfer submission	Submit the transfer from your backend when the SDK requests it. See Your backend's responsibilities.	Validates and processes the transfer.
Status updates	Expose an endpoint, return `2XX` on receipt, and update your records. See Transfer status updates.	Sends a status update each time a transfer's status changes.
Screening outcomes	Handle the resulting transfer statuses, and return funds to the sender's account when a transfer is canceled.	Screens transfers and sets the transfer status.
Receipts and disclosures	Review the required sections in receipt compliance.	The SDK displays the disclosures and the receipt.
Error handling	Handle API errors and SDK error events. See Exception handling.	Returns error codes and messages.

Next steps

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

Your backend's responsibilities: build each backend step in order.
Implementation overview: the technical phases from credentials to go-live.
Security and trust: credential handling, tokens, and portal SSO.