Español | Português | Русский | Français | Italiano

Translations may be outdated.
Las traducciones pueden estar desactualizadas.

Open-source, modular, and agnostic-by-design payment infrastructure for businesses and users that need practical multi-rail payment flows, self-custodial settlement, and more flexible cross-border money movement.

P2Pagos is built around inbound rails, multi-rail offramp and self-custodial settlement. It is designed to make payment architecture more practical across markets, rails, currencies, and jurisdictions, especially where traditional payment access is fragmented, limited, or overly dependent on a single provider.

P2Pagos uses BTCPay Server as the backend and an Aqua Wallet fork as the default settlement wallet.

BTCPay Server was chosen because it is a battle-tested, widely adopted, and community-maintained API and GUI backend with some built-in rails. We also actively contribute to its core and plugin ecosystem.

Aqua Wallet was chosen because it already supports settlement in btc on-chain, multiple stablecoins (USD and BRL for now) by default, and can be integrated from BTCPay Server through the Shamrock protocol with a QR-based connection flow.

Where direct local cashout is not yet native, P2Pagos provides practical guidance around compatible external wallets, cards, and off-ramp tools to improve real usability in Latin America and other supported regions. For instance, across all currently planned settlement chains, we already consider wallets and services such as Belo, Revolut, and Offramp, including card and Google Pay / Apple Pay compatible paths, while more privacy-friendly card and Google Pay options may later be added through planned FixedFloat API work or collaboration with the issuer.

P2Pagos is designed around a few practical choices:

• Self-custodial by default
• Agnostic in practice — the usable rail and settlement path matter more than ideology
• Multi-rail by design — different markets need different ways to pay and cash out
• Modular — inbound rails, offramps, flows, and services can be enabled or left out depending on the use case
• Open source — the public components remain MIT licensed, with long-term maintenance and development supported by revenue from the paid closed-source offering

If an inbound rail does not already settle into an asset supported by the Aqua wallet fork, P2Pagos aims to convert further into the supported asset that is cheapest and most functional for that case.

flowchart LR

subgraph walletWrap["/wallet (MIT)"]
  walletPlatform["Aqua fork (MIT) / (iOS & Android)"]
  seedMono["seed phrase"]
  seedMarket["seed phrase"]
  seedTeam["seed phrase / xpub"]
end

mono["/mono (MIT)"]
monoBtcpay["BTCPay Server (MIT)"]

subgraph docker["Docker"]
  marketplace["/marketplace (closed-source)"]
  marketBtcpay["BTCPay Server (MIT)"]
  bridge["/bridge"]
  kyc["/kyc"]
  pyCompliance["/py-compliance"]
end

team["/team"]
otherWallet["/wallet (MIT)"]
builtMarket["built on"]
builtTeam["built on"]

dashboard["/dashboard (MIT)"]

seedMono --> mono
seedMarket --> marketplace
seedTeam -.-> team
otherWallet --> marketplace

mono --> monoBtcpay
marketplace --> marketBtcpay
dashboard --> marketplace

marketplace -.-> builtMarket
builtMarket -.-> mono

team -.-> builtTeam
builtTeam -.-> mono

marketplace --> bridge
marketplace --> kyc
marketplace --> pyCompliance

style team stroke-dasharray: 6 6
style builtMarket fill:transparent,stroke:transparent,color:#999
style builtTeam fill:transparent,stroke:transparent,color:#999
style walletPlatform fill:transparent,stroke:transparent,color:#999

click otherWallet "https://github.com/P2Pagos/wallet" "_blank"
click mono "https://github.com/P2Pagos/mono" "_blank"
click bridge "https://github.com/P2Pagos/bridge" "_blank"
click kyc "https://github.com/P2Pagos/kyc" "_blank"
click pyCompliance "https://github.com/P2Pagos/py-compliance" "_blank"

Closed-source repos are only available to team members and not to external collaborators. Some modules may be open-sourced at a later stage.

These integrations are closed source because they require enhanced verification for the marketplace admin and for users involved in high-value transactions. They also finance all open-source development.

For these integrations, Blockchange.expert can advise a structured plan either under a Paraguay EAS or a US LLC. This consultancy service is ready to deploy today by booking an integration call at https://www.blockchange.expert/en/#call or by email asynchronously.

Referral code for one month free: Freedomia

Single user orchestrator MIT repository.

It assembles inbound rails, settlement flows, and supporting services into one workspace. Active development is currently centered here.

A MIT fork of the Aqua Flutter Wallet for P2Pagos, with an embedded Nuxt app to manage /mono settings and connect to BTCPay via the Shamrock protocol.

Nuxt-based MIT app, intended to handle payment flows through an embedded interface in the /wallet Flutter app.

Closed-source repository for multi-user marketplace integrations of the /mono repo.

Closed-source integration module for Bridge.xyz-based fiat reception and payout orchestration within marketplace flows.

Closed-source integration module for enhanced verification, admin-level checks, and user onboarding flows tied to high-value marketplace transactions.

Closed-source Paraguay-specific module for accounting, reporting, and local compliance-oriented marketplace operations.

Some of the clearest use cases are already emerging from our immediate network.

• A construction company opportunity is already active through Marta, with real demand for receiving higher-value crypto payments in Paraguay.
• A content creator with an international audience in the health and wellness space wants to open an agency for local businesses that want to rank better on Google Maps, appear in featured snippets, and manage DNS-related work. In that flow, P2Pagos can be the payment method, while the businesses paying him may be located in Paraguay, broader LATAM, or even the Philippines.
• During a recent weekend in the Chaco, another close Italian contact described two business lines that fit our payment approach very well:
  • assistance with Paraguayan paperwork such as cédula, residency, driver’s license, certificado de vida y residencia, and RUC opening
  • a low-cost hostel for backpackers and digital nomads booking from abroad without local Paraguayan bank accounts

Some of these businesses may be considered high-risk by mainstream payment processors even when they are not inherently problematic. Our payment method fits them well precisely because it is settlement-first, cross-border, and less dependent on local banking constraints.

P2Pagos is aimed at cases where standard payment stacks are too limited, too fragile, or too dependent on a single provider.

Typical use cases include:

• cross-border businesses
• businesses that need multi-rail inbound payments
• merchants that want crypto settlement with broader payment reach
• users in emerging markets
• high-risk but lawful businesses
• builders that want modular, self-hostable payment infrastructure
• Bitcoiners and crypto enthusiasts

It is not meant to be presented as a universal fit for every merchant.

P2Pagos is still evolving.

Some components exist as working integrations, others are partial, experimental, or still being assembled into the main orchestrator. The repositories should be read as active infrastructure work, not as a finished product suite.

• GitHub Discussions
• Telegram Group
• p2pagos@p2pay.to with optional PGP A1786A2CF6C5B65FDB4519F17E425F745D4EE866