Map your complete payment
Your structure. Your labels. One reusable map.
The mapper is not supported on mobile
Use a desktop browser with a wider window to build your map.
Start with your payment JSON
Assemble the payment details, parties, and documents in the shape you intend to send. Include every field you may use, with fictional values. For lists, show one entry for each different structure.
Prepare your payment structure ↓Data you’ll connect
Payment details
Funding account, amount and currency, plus any purpose, source of funds, or references.
Sender
The client paying through you, including their identification and related individuals. If you use the API to pay for yourself, no sender object is needed.
Recipient
The beneficiary, receiving account, and bank details.
Documents
Each file needs a document type, filename, and base64 content, plus a clear connection to what it proves.
Your payment structure
Use your own field names and nesting. The example shows one possible structure.
JSON only, up to 2 MB. Use small fictional file contents. Changes stay in this tab until you download them.
Prepare your payment structure
Start from your records, make the document links clear, and choose a shape you can reuse for every payout.
Include the fields you’ll send
Use your own field names and nesting. Include optional fields your integration may send, with fictional values. For lists of people or files, show an entry for each different structure.
Show where each file belongs
Choose whichever arrangement is easiest for your integration: nest files with the records they support, keep them in a separate list, or use a combination of both.
AI will examine your JSON and propose where each file belongs. Your data must provide a clear, repeatable link to the right party, person, identification, or payment—through nesting, matching IDs, or identifying tags.
You review and confirm the proposed connections. If a link is missing or ambiguous, the tool will ask you to clarify it.
Reuse the shape as values change
Names, amounts, IDs, and list lengths can change with each payment. Keep the same field paths and rules for connecting documents.
Supply your possible codes and labels separately in Values, for fields such as purpose and document type. Names, references, and amounts do not need a list of possible values.
Prepare your JSON with AI
OptionalGive this prompt to an AI assistant with access to your data sources, record schemas, or example exports. It helps assemble the payment JSON, identify missing data, and make document ownership explicit.
The prompt includes documentation links and your sender choice. Your payment JSON is not included. Review the proposed structure before using it.