Pix payout passport for global marketplaces paying Brazilian sellers, packaging FX evidence for every stablecoin-funded payout.

1. Brazil classifying virtual-asset cross-border flows as FX operations means platforms need bank-grade corridor evidence, not just faster settlement.
2. Trace's core product claim is that stablecoins only work when paired with local-bank and compliance orchestration, which surfaces a missing workflow layer above the rail.
3. More than $10B processed in the US-Brazil corridor shows the workflow is already large enough for vertical software rather than a future infrastructure bet.
4. Trace serving top global payment providers including dLocal proves sophisticated platforms still externalize corridor complexity and gives the startup a clear partner-led distribution surface.
5. The GENIUS Act and Hong Kong Stablecoin Ordinance broaden the regulated stablecoin corridor opportunity beyond one country, making this a category-formation moment.

Catalyst. Brazil's FX classification change, Trace's $10B-plus proof in the US-Brazil corridor, and enterprise expansion around Pix-plus-stablecoin infrastructure make corridor-specific payout control software newly urgent.

Build a workflow layer between the platform payout ledger, onboarding and KYB systems, ERP, and regulated payout partners such as Trace-like providers. For each beneficiary and batch, it verifies tax IDs, payout purpose, corridor rules, and whether the payout should land via Pix-linked bank rails or another local method, then attaches the required evidence before funds are released. It maintains a reusable beneficiary-passport record so repeat payouts stop generating fresh compliance tickets. Ops teams get a case queue for rejected bank data, mismatched purpose codes, and failed local-rail handoffs, while finance gets journal-ready FX and fee reconciliation. Over time, the product becomes a multi-corridor rules engine and system of record for global platform payouts.

What's different. This is not another stablecoin API, local payout processor, or treasury dashboard. The product owns the customer-side workflow that regulated partners still push back onto the platform: beneficiary passporting, purpose-code logic, corridor rules, and evidence packaging before payout release. That creates a defensible corpus of payout eligibility rules, exception patterns, and local-rail playbooks that becomes more valuable with each new corridor.

Jobs to be done

flowchart LR
  Buyer[Marketplace payout ops lead] --> Pain[Brazil payouts stall on FX and beneficiary checks]
  Pain --> Product[Pix payout passport]
  Product --> Outcome[Same-day local payout with audit-ready release]

Executive takeaways

• [2][8][3] The wedge is not access to stablecoins; it is packaging release-ready beneficiary, FX, and audit evidence so Brazil payouts can actually clear under partner and regulatory constraints.
• [26][9][30] Pix makes payout speed table stakes, but local-entity rules, IOF, eFX intermediation, and CPF/CNPJ data requirements keep Brazil launches operationally messy for foreign platforms.
• [16][12][1] Supply-side infrastructure is already live across USDC, licensed payout partners, and local-bank rails, which means provider-neutral workflow software can sell now rather than wait for ecosystem maturity.
• [7][19][10] Budget can come from seller-retention, payout-ops, and finance-control lines because faster payouts and cleaner stablecoin workflows already show measurable value, not just speculative crypto upside.

Market definition

[1][8][16] The relevant market is corridor-control software for platforms and payout providers that fund cross-border value with stablecoins but still need local-bank or Pix release workflows, beneficiary passporting, and audit-ready evidence before money lands in Brazil.

Customer and buyer

[7][8][87] Daily users are payout operations, finance systems, and compliance teams at global marketplaces, creator platforms, and payout networks paying Brazilian sellers or creators. The economic buyer is typically a VP Finance, controller, or Head of Global Payouts who owns seller experience, release risk, and close quality.

Buying triggers

• A Brazil launch, same-day Pix rollout, or rising seller cash-out demand exposes that the platform cannot self-serve compliant payouts into Brazil through its default PSP stack. [8][26][9]
• Repeated payout holds or support escalations make payout speed, FX transparency, and documentation quality visible to finance and seller-growth leaders. [7][35][36]
• A treasury team adopts stablecoin funding or evaluates providers like Trace, Circle, or Nium, forcing the business to define approval, routing, and reconciliation controls above the rail. [2][16][12][4]

Willingness to pay

Willingness to pay should come from a mix of seller-retention urgency and finance-control ROI. Visa’s marketplace research shows most digital entrepreneurs would consider switching platforms for better payout options and many would pay for instant payouts, while EY and PwC show enterprise stablecoin users already reporting cost savings and treasury interest. That makes this easier to budget as payout-ops, finance transformation, or control software than as a standalone crypto experiment. [7][19][87][36]

Category dynamics

Growth signal ~93% implied CAGR in projected cross-border B2B stablecoin transaction value (2026-2035)

Validation signals

• Trace says it has already processed more than $10B in cross-border volume and serves top LatAm payment providers, proving real commercial demand for regulated corridor infrastructure.
• Circle CPN is live with Alfred Pay for USDC-to-Pix offramps in Brazil, showing that stablecoin-to-local-rail delivery is already operational.
• Nium’s Brazil license and USDC settlement partnership with Circle show global payout networks are moving toward direct regulated-local plus stablecoin-settlement combinations.
• Visa’s payout research shows sellers are willing to switch platforms and even pay a small fee for better or instant payout experiences.
• EY found that a meaningful share of existing stablecoin users already report 10%+ cost savings, indicating this is no longer a purely speculative buyer conversation.

Regulatory & technical constraints

• BCB Resolution 561 restricts eFX providers from using stablecoins or crypto to settle cross-border payments inside the regulated framework, pushing deployments toward authorized bank or payment-institution structures.
• Pix access and acceptance still come with local-entity, participant, or licensed-partner requirements that foreign platforms cannot ignore.
• International Pix-linked flows can trigger IOF and eFX documentation requirements, making FX evidence and partner data quality central product requirements.
• Structured messaging and API harmonization requirements mean payout data cannot stay in free-text ops workflows if the product is meant to integrate cleanly with banks and local rails.

[1][15][6][13][23] Competition is strategic rather than category-pure: regulated payout rails, stablecoin orchestration vendors, and global PSPs are all expanding toward the same release-control surface. The substitute remains one rail provider plus spreadsheets, tickets, and month-end reconciliation until Brazil volume and seller pain make that operating model crack.

Why incumbents do not win by default

• Regulated payout rails. Trace, Nium, Circle CPN, and similar providers can move money compliantly, but they are structurally optimized to drive flow through their own network or partner stack rather than serve as a neutral control plane across multiple payout partners.
• Global PSPs and local methods. Stripe, Adyen, EBANX, and local payout processors validate demand, yet Brazil remains invite-only, partner-dependent, or local-entity constrained for many use cases. That leaves the customer still owning beneficiary passporting and release prep.
• Stablecoin orchestration vendors. Bridge, BVNK, and Zero Hash abstract wallets, liquidity, and local delivery well, but they generally start from execution and network reach rather than from the finance-owned workflow that maps seller context, payout purpose, and audit evidence before release.
• In-house ops plus ERP. The default substitute is still one PSP plus spreadsheets, tickets, and manual close work. Buyers will keep using that stack until payout delays, support load, or bank scrutiny becomes expensive enough to justify dedicated software.

Pix Payout Passport sells a neutral control layer for global marketplaces and creator platforms that fund Brazil payouts from centralized treasury flows but still need bank-grade release evidence before BRL can land through Pix. Brazil's 2026 FX classification change and Trace's $10B-plus corridor proof mean the settlement stack now exists, but customer-side beneficiary passporting, purpose-code mapping, and audit packet assembly remain manual. The first wedge is U.S.- and European-based platforms paying 500-5,000 Brazilian sellers or creators per month that want same-day Pix cash-outs without building a Brazil FX operations team. The MVP should stay above funds flow and focus on pre-flight checks, exception routing, and journal-ready evidence because that is the workflow buyers still own even when they use Trace-, Nium-, or Circle-linked partners. Go-to-market should center on founder-led sales into Brazil launches and payout-hold incidents, with referrals from regulated payout partners that want cleaner beneficiary and FX data but do not want to become the customer's full control plane. Pricing should follow enterprise control-software logic rather than payment spread: paid corridor-launch implementation plus six-figure annual software priced by corridor, legal entity, and verified-beneficiary or protected-volume bands. The main diligence gaps are exact bank rejection baselines, the payout-volume threshold at which buyers abandon PSP-plus-spreadsheet workflows, and whether neutral workflow software can win against partner bundling. This is strong enough for further investigation because the wedge is specific and timely, but the company should raise only a pre-seed round until it proves two paid pilots and one partner-backed deployment.

Problem

• Brazil stablecoin-linked payouts require beneficiary, payout-purpose, and FX evidence that most global platforms still manage in spreadsheets, tickets, and PSP dashboards.
• When same-day Pix launches or payout holds spike, finance and payout operations teams lose seller trust and spend hours assembling audit and reconciliation evidence across rail partners and the ERP.

Solution

• A Brazil corridor passport creates a reusable beneficiary record linking CPF/CNPJ, KYB, bank or wallet routing, approved payout-purpose codes, and partner-specific release requirements before each batch is sent.
• The workflow layer runs pre-flight checks, exception queues, and batch-level FX, fee, and journal exports across payout ledgers, ERPs, and regulated bank partners so live payouts and month-end close use the same source of truth.

Why we win

• Incumbent rails and stablecoin orchestration vendors optimize for moving money through their own network, not for giving the platform a neutral control plane across multiple partners.
• Every protected batch builds a proprietary graph of beneficiary eligibility, exception patterns, and partner documentation rules that becomes harder to replace than the payout rail itself.
• By staying above funds flow at launch, the company can ship faster, remain provider-neutral, and avoid taking Brazil licensing or balance-sheet risk.

Milestones

flowchart LR
  Wedge[Brazil corridor passport wedge] --> MVP[Pre-flight and evidence MVP]
  MVP --> Proof[Lower holds and faster close proof]
  Proof --> Expansion[Multi-partner and multi-corridor expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 5 of the first 12 target buyers confirm a dedicated budget owner for Brazil payout controls before they build an internal ops team.
• The first 3 customers see at least a 50% drop in manual exception handling or evidence-assembly time on Brazil payout batches.
• A licensed bank or payment-institution partner will share enough release-status and documentation logic for the startup to encode repeatable rules.
• At least 2 rail or payout partners tolerate and support a neutral workflow layer instead of blocking it in favor of bundled tooling.
• An adjacent corridor can reuse at least 60% of the Brazil data model and workflow within 18 months.

Open diligence questions

• What are current hold and rejection rates for Brazil payout batches, and which reasons dominate?
• Who actually signs budget and security approval when a platform launches same-day Pix payouts?
• How much provider-specific logic sits outside published APIs and must be learned through services?
• Will Trace-, Nium-, Circle-, or local bank partners co-sell a neutral control layer or race to bundle it?
• How portable is the beneficiary-passport model to Mexico or Colombia without resetting implementation cost?

Model sanity

• Revenue engine. Base-case revenue is driven mainly by logo adds from 3 customers at Y1 exit to 12 at Q4Y2 and 26 at Q4Y3 on a $150K annual ARPU.
• Must go right. Partner-backed pilots must convert quickly enough to hit the top end of the BP 8-12 customer Y2 target before GTM hiring steps up.
• Model breaks if. The downside case turns cash negative if the sales cycle slips by about two months and pricing settles closer to $140K per customer-year.
• Next-round proof. The next financing story is credible if the pre-seed gets the company to roughly 7 paying Brazil customers, one partner-backed annual deployment, and repeatable sub-30-day implementations.

Scenarios

Sensitivity

flowchart LR
  Leads[Founder-led + partner referrals] --> Pilots
  Pilots --> Customers
  Customers --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: The model assumes no realized logo churn through Y3; churn is used for LTV math only until the first renewals are observable. · Q4Y2 lands at the top end of the BP 8-12 customer milestone, so partner-sourced pipeline and pilot conversion must both work on schedule. · Gross margin stays near target only if implementation work standardizes; if services intensity remains high, both COGS and hiring would drift upward. · Cash is modeled as EBITDA-driven and does not reflect deferred revenue timing, collection lag, or capex, which could move the cash curve modestly earlier or later.

• Provider bundling. Trace, dLocal, or another PSP could add basic beneficiary and corridor checks inside their own platform. Mitigation: Stay provider-neutral and own the cross-system workflow, reusable beneficiary passport, and ERP evidence layer that customers need across multiple partners and corridors.
• Regulatory drift. Brazil or later corridor rules may change faster than the product can encode them, creating trust risk for finance teams. Mitigation: Start with one corridor, version rules with local advisers and bank partners, and keep human-approved exception paths before deeper automation.
• Narrow initial wedge. Some marketplaces may not feel enough pain until Brazil payout volume or rejection rates are already high. Mitigation: Sell during corridor launches and same-day payout rollouts, quantify seller churn and ops cost from held payouts, and expand first into adjacent LatAm corridors where the same customer can reuse the platform.