How to Map Payment Flows to Determine Fintech Licensing & Bank Readiness in Panama (step‑by‑step, 2026)

Understanding how to map payment flows for FinTech licensing in Panama is now an operational prerequisite for any company that intends to process, settle, or custody funds through the Panamanian financial system. The Superintendencia de Bancos de Panamá (SBP) has signalled, through the launch of its Fintech Hub and the rollout of SBP Rule 1‑2026, that banks must request detailed payment‑flow diagrams before onboarding FinTech clients. At the same time, Draft Law No. 314 (Anteproyecto, Ley Marco Fintech) introduces activity‑based licensing triggers that turn directly on the type of flows a company operates.

This guide walks founders, product leads and general counsel through the complete payment flow mapping process, from initial diagramming to bank‑pack assembly to formal pre‑filing with the SBP, with timelines, documents and costs current as of mid‑2026.

Overview of the Process and Who It Applies To

Payment flow mapping is the discipline of diagramming every movement of value, and the data that travels with it, across your product. Each node in a flow represents a participant (payer, merchant, payment service provider, acquiring bank, correspondent bank) and each edge represents a rail (card network, ACH transfer, mobile wallet top‑up, blockchain settlement, wire). By mapping these elements visually and narratively, a FinTech translates its product mechanics into the language that regulators and banking compliance teams use to assess risk.

In Panama, the payment methods available to FinTechs include domestic ACH (Sistema de Pagos de Panamá), international card networks, SWIFT and correspondent banking rails, mobile money channels, and, increasingly, crypto‑to‑fiat conversion rails. Each of these channels carries distinct regulatory implications. A simple four‑node flow, for example, might show: (1) customer funds a wallet via bank transfer, (2) funds are held in an omnibus account at a Panamanian bank, (3) funds are converted from USD to a stablecoin, and (4) the stablecoin is sent to a merchant’s wallet. Even this straightforward sequence touches custody, foreign‑exchange conversion, and e‑money issuance, three separate licensing triggers under Draft Law No. 314.

Every FinTech that seeks a Panamanian bank account or any form of SBP‑supervised licence should begin mapping before bank outreach, not after. The SBP Fintech Hub now operates as a pre‑filing touchpoint where companies can present early‑stage diagrams and receive directional guidance before committing to a formal application track. Starting the mapping process early, ideally during late product design, saves weeks of remediation later.

Who must map?

The short answer: any entity that moves, holds, or converts value through Panama and needs banking access. This includes payment service providers (PSPs), electronic money issuers (EMIs), remittance operators, crypto exchanges with fiat on/off ramps, and lending platforms that disburse or collect through Panamanian accounts. If your product touches Panamanian settlement rails or serves Panamanian end‑users, the SBP will expect a payment‑flow diagram as part of its supervisory assessment.

Eligibility, Prerequisites and Licensing Triggers

Before beginning the mapping exercise, a company must understand the activity categories that create licensing triggers under Panama’s evolving regulatory framework. Draft Law No. 314 adopts an activity‑based approach: the licence requirement is determined not by corporate form or domicile, but by what the company does with funds.

Activity categories and decision‑tree logic

The following categories are the primary licensing triggers that payment flow mapping is designed to identify:

• Payment services. Initiating, processing, or settling payment transactions on behalf of third parties. If your flow shows funds moving from a payer through your platform to a payee, you are likely providing a payment service.
• Custody of funds. Holding customer funds for any period, even momentarily in an omnibus account, before forwarding them to a recipient. The longer the hold and the larger the aggregate balance, the higher the regulatory tier.
• Electronic money issuance. Issuing a stored‑value instrument (prepaid card, digital wallet balance, stablecoin pegged to fiat) that represents a claim on the issuer. If your flow includes a “top‑up” step where customer funds are converted into a platform‑native balance, this trigger is engaged.
• Foreign‑exchange or crypto conversion. Converting between currencies, including fiat‑to‑crypto or crypto‑to‑fiat, as part of the payment flow.
• Remittances. Cross‑border transfer of funds on behalf of individuals, particularly where the destination or origin is Panama.

A practical decision tree works as follows: if your flow diagram shows that you hold customer funds, settle with a Panamanian merchant, custody private cryptographic keys, or issue stored value, the likely practical effect will be that a full PSP or EMI licence is triggered. If your platform merely provides technology infrastructure (APIs, routing logic) without touching funds, a lighter registration or exemption may apply. The SBP Fintech Hub engagement, described in Step 6 below, is the mechanism for confirming which tier applies to your specific flow.

Step‑by‑Step Procedure: How to Map Payment Flows for FinTech Licensing in Panama

The payment flow mapping process follows six sequential steps. Each step produces a discrete deliverable that feeds into the bank‑pack and regulator‑pack described in the documents section below. Industry observers expect that companies arriving at bank meetings or SBP pre‑filings with all six deliverables complete will move through diligence materially faster than those presenting incomplete or marketing‑oriented documentation.

Step 1, Catalogue all product flows: inbound rails, conversions, and outbound rails

Begin by listing every path that value can take through your product. For each path, record the inbound rail (how the customer’s funds enter your system), any mid‑flow conversions (currency exchange, fiat‑to‑stablecoin, aggregation into omnibus accounts), and the outbound rail (how funds reach the final recipient). Layer this information into a master payment‑flow diagram using standard notation: rectangles for entities, arrows for fund movements, diamonds for decision points, and annotations for currency, volume estimates, and settlement timing. The deliverable at this stage is a single‑page visual diagram with a legend, plus a tabular breakdown listing each flow path, the currencies involved, and the estimated monthly transaction volume.

Step 2, Identify all participants and data flows

For every node on your diagram, create a participant register entry. Record the entity’s legal name, jurisdiction of incorporation, regulatory status (licensed, registered, or unregulated), and its role in the flow (payer, payee, merchant, acquiring bank, correspondent bank, PSP, liquidity provider). Mark each participant as resident or non‑resident relative to Panama. This entity‑type map is critical because the SBP and onboarding banks will assess counterparty risk at the entity level. If a key participant is unregulated in its home jurisdiction, expect additional diligence questions. The deliverable is a participant register table linked to the diagram nodes.

Step 3, Tag activity types to regulatory triggers

With flows and participants documented, overlay the licensing trigger categories from Draft Law No. 314 onto each leg of the diagram. For every flow segment, ask: does this leg involve custody, payment initiation, settlement, conversion, or stored‑value issuance? Record the answer in a trigger table that maps each activity to the potential licence type or SBP interest it generates. A single product can trigger multiple categories. The deliverable is a trigger table structured as follows:

Step 4, Map AML/CTF controls and KYC points onto the flow

Panama’s Unidad de Análisis Financiero (UAF) requires reporting entities to file suspicious activity reports (SARs) and suspicious transaction reports (STRs) when thresholds or behavioural indicators are met. Your payment‑flow diagram must show exactly where AML/CTF controls are applied: at customer onboarding (KYC identity verification), at each top‑up or deposit (transaction monitoring), at conversion points (enhanced due diligence for high‑value or cross‑border conversions), and at payout (sanctions screening). The deliverable is a control matrix overlaid on the flow diagram, specifying the control type, the threshold or rule that triggers it, and the escalation path if an alert fires.

This is one of the most scrutinised elements in any bank diligence process and will be directly tested against AML/CTF requirements set out in SBP circulars on prevention.

Step 5, Produce the bank‑pack and regulator‑pack

Compile Steps 1–4 into two submission‑ready packages. The bank‑pack is the document set presented to commercial banks during onboarding meetings; the regulator‑pack is the document set submitted to the SBP (either via the Fintech Hub or as part of a formal licence application). Both packs share the same core, the master flow diagram, participant register, trigger table, and AML control matrix, but differ in supporting documents. The bank‑pack adds proof of funds, founder KYC, and signed counterparty contracts. The regulator‑pack adds the formal application form, regulatory capital evidence (if required), and the local agent letter. The documents table in the next section provides the full checklist.

The deliverable is two indexed PDF bundles, each with a cover letter and table of contents.

Step 6, Execute the pre‑filing and bank engagement sequence

With packs assembled, follow this engagement sequence: first, submit a pre‑filing enquiry to the SBP Fintech Hub with the regulator‑pack. The Fintech Hub provides directional guidance on which licence category applies and whether the SBP has specific documentation expectations. Second, once SBP guidance is received (or in parallel if timelines are tight), approach at least two Panamanian banks with the bank‑pack. Present the flow diagram in person or via a structured video call, walking the bank’s compliance team through each leg and control point. Third, respond to bank and SBP follow‑up queries, these typically focus on counterparty due diligence, volume projections, and AML escalation procedures.

Fourth, if a formal licence application is triggered, submit the complete regulator‑pack to the SBP through the prescribed channel. The table below summarises who does what and the typical duration for each step.

Required Documents for Payment Flow Mapping and Bank Onboarding

The documents needed for both the bank‑pack and the regulator‑pack are listed below. Every document should be prepared in PDF format unless the recipient specifies otherwise. Foreign‑issued corporate documents must be apostilled. Translations into Spanish are required for any document not originally in Spanish or English, depending on the bank’s policy. The table indicates who issues each document, the expected format, and any validity constraints.

Banks conducting FinTech onboarding diligence will cross‑reference the flow diagram against the contracts, the AML policies, and the technology architecture. Any inconsistency, for example, a flow leg that references a liquidity provider not covered by a signed contract, will stall the process. Assemble documents in parallel with the mapping steps above, not sequentially after them.

Timeline and Key Deadlines for Payment Flow Mapping and Licensing

The overall timeline runs on two parallel tracks: (A) bank onboarding, which is operationally driven and depends on the bank’s internal diligence speed; and (B) licensing, which is regulatory and depends on the SBP’s review capacity and application completeness. Running both tracks simultaneously, rather than waiting for a licence before approaching banks, is standard practice and is encouraged by the SBP’s Fintech Hub model.

Choosing a bank and non‑resident access

No single Panamanian bank is universally “best” for foreign FinTechs. Banking access depends on the company’s risk profile, flow complexity, and transaction volumes. Industry observers expect that approaching at least two to three banks simultaneously, presenting the full bank‑pack at each meeting, is the most efficient path. Some banks accept non‑resident corporate accountholders, but enhanced due diligence applies: expect requests for a local representative, additional UBO documentation, and longer review timelines. Founders who cannot be physically present in Panama for meetings should engage a local legal representative authorised to act on their behalf during the onboarding process.

Costs, Fees and Tax Considerations

The costs of payment flow mapping, bank onboarding, and licensing in Panama vary significantly depending on flow complexity, the number of licensing triggers engaged, and the banks approached. The table below provides indicative ranges. All figures are in USD and should be verified against current SBP fee schedules and individual bank policies before budgeting.

Tax considerations are flow‑specific. FinTechs operating payment or remittance services in Panama should consult with local tax advisers on transfer pricing, withholding obligations on cross‑border payments, and the applicability of Panama’s territorial tax system to digital‑service revenues. These issues sit outside the payment flow mapping exercise but should be addressed in parallel during company structuring.

What Changes in 2026: Draft Law No. 314 and SBP Rule 1‑2026

Two regulatory developments in 2026 make payment flow mapping more consequential than in prior years. Understanding these changes is essential context for anyone working through the steps above.

Draft Law No. 314 (Ley Marco Fintech), This framework FinTech law, currently progressing through Panama’s Asamblea Nacional, introduces activity‑based licensing. Rather than a single catch‑all licence, the draft law establishes tiered categories, including payment services, electronic money issuance, crowdfunding, and digital asset services, each with proportional capital, governance, and reporting requirements. The practical impact for payment flow mapping is direct: your trigger table (Step 3 above) now maps to specific licence categories with defined obligations, rather than to a general supervisory expectation. Early indications suggest that flows involving custody of customer funds in local currency or merchant acquiring with domestic settlement are the most likely to trigger the higher‑tier licence requirements.

SBP Rule 1‑2026, The Superintendencia de Bancos issued this rule to strengthen banks’ capacity to assess and onboard FinTech clients. Under this rule, banks are expected to request detailed payment‑flow diagrams and AML control matrices from FinTech applicants as part of their onboarding diligence. The SBP has also expanded the Fintech Hub as a structured pre‑filing channel where companies can present flows before formal application. The likely practical effect is that banks will increasingly treat the absence of a detailed flow diagram as a reason to decline onboarding, and the Fintech Hub engagement will become a de facto prerequisite for smoother bank introductions.

Together, these 2026 developments mean that the quality and completeness of your payment flow map directly determines both the speed of banking access and the cost and scope of your licensing obligation under the Panama 2026 FinTech law framework.

Common Pitfalls and How to Avoid Them

• Vague or marketing‑style diagrams. Banks reject onboarding requests when the flow diagram uses promotional language instead of operational detail. Use standard symbols, include a legend, annotate each leg with transaction volumes and settlement SLAs, and present the diagram as a technical document, not a pitch deck.
• Missing counterparty documentation. Every entity on the flow diagram must be backed by a registry extract and, where applicable, a signed commercial contract. If a liquidity provider or acquiring bank appears on the diagram but is not supported by documentation, the bank’s compliance team will flag a gap and pause the review.
• Ignoring UAF reporting thresholds. Failing to map SAR/STR alert thresholds to the flow diagram is a common omission. The UAF expects reporting entities to demonstrate that monitoring rules are calibrated to the specific transaction types and volumes in their flows. Include sample monitoring rules and escalation procedures in the AML control matrix.
• Presenting product marketing instead of operational evidence to banks. Banks need to see the narrative, the technology architecture diagram, reconciliation screenshots, and sample KYC records, not a product brochure. Operational evidence of controls already working (even in a test environment) is far more persuasive than a description of what the company intends to build.
• Sequencing bank outreach before completing the flow map. Approaching a bank without a complete bank‑pack wastes the first meeting and can create a negative impression that is difficult to reverse. Complete Steps 1–5 before scheduling the first bank meeting.

Conclusion

Learning how to map payment flows for FinTech licensing in Panama is no longer an optional planning exercise, it is the foundational step that determines the scope of your licensing obligation, the speed of your banking access, and the cost of your compliance build. The six‑step process outlined above, from cataloguing product flows and tagging licensing triggers through to assembling the bank‑pack and engaging the SBP Fintech Hub, provides a structured, repeatable method for translating product mechanics into the regulatory and banking documentation that Panama’s financial system now demands. With Draft Law No.

314 and SBP Rule 1‑2026 reshaping the landscape in 2026, companies that invest in rigorous, early‑stage payment flow mapping will navigate the process faster and at lower cost than those that treat it as an afterthought.

Sources

1. Superintendencia de Bancos de Panamá, Fintech Hub
2. Superintendencia de Bancos de Panamá, SBP Rule 1‑2026 Implementation
3. Gaceta Oficial Digital (Panama)
4. Unidad de Análisis Financiero (UAF), Panama
5. IMF, Panama: Technical Note on AML/CFT