Loading...
Supporting developers, startups, and full-fledged companies building on Stellar and Soroban
© 2026 Stellar Development Foundation
Subscribe to the Newsletter
By Bexo Wallet — USDC Payments, Cross-Border Transfers & QR Merchant Payments for Latin America
1. Native Stellar USDC Wallet Each Bexo user gets a self-custodial Stellar USDC wallet linked to their existing verified identity. Stellar is used for account creation, trustline setup, and native send/receive via Horizon API — no gas complexity exposed to the user. Impact: brings Stellar's speed and cost efficiency directly into an app with 3K+ monthly active users, with zero onboarding friction.
2. ARS ↔ Stellar USDC Ramp Bridge Bexo's existing proprietary ARS ramp — already one of the top-3 rates in Argentina — is connected to Stellar accounts. Users buy and sell USDC that settles natively on Stellar. Impact: transforms Stellar USDC into a practical dollarization tool for Argentine users, not a crypto-native experiment.
3. Stellar USDC Top-Up for Foreign Users + Argentine QR Payments Eligible foreign-user profiles can fund a custodial USDC balance via Stellar USDC top-up, then pay at any Argentine QR merchant (BCRA standard) with zero merchant onboarding required. Stellar is the funding rail; existing payment infrastructure handles the last mile. Impact: unlocks real-world merchant payments in Argentina settled through Stellar, targeting 350+ QR payments in the first 30 days post-launch.
4. Simple Earn (Blend Protocol / Soroban) Users deposit Stellar USDC and earn variable yield via Blend Protocol on Soroban, displayed as a simple APY with full risk disclosure — no DeFi knowledge required. Impact: positions Bexo against Mercado Pago's ~2% APY with a dollar-denominated yield product accessible to mass-market users.
5. NEAR Intents Extension for Stellar USDC Routes Bexo's existing NEAR Intents integration is extended to include Stellar USDC as a source and destination asset for cross-chain routing where routes are available. Fallback behavior is implemented when no Stellar route exists. Impact: adds interoperability between Stellar and other supported chains inside a flow users already trust.
$90.0K
Bexo Wallet is a live product with verifiable traction:
METRICS (last 90 days operations)
- $1.5M USD in transaction volume
- 9,000 downloads (iOS + Android)
- 3,000+ monthly power users with daily usage
- Volume growing day over day
LIVE FEATURES (verifiable in production)
- USDC savings and swaps on Polygon and RSK
- Nickname-to-nickname self-custody cross-chain transfers (no wallet address needed)
- E2E encrypted chat payments
- QR payments at existing native merchant QRs in Argentina (BCRA), -Coming next: Brazil (PIX) and Paraguay -
TEAM TRACK RECORD
- Ezequiel Cuesta (CEO): early Xapo Bank employee,
led growth and infrastructure from 0 to Millions transactions. In blockchain/fintech since 2013.
- 5 chain integrations shipped to production:
Bitcoin Native, Ethereum native
- Stellar local testing completed pre-submission:
Horizon API, Ed25519 key generation and
on-device signing validated in Bexo's stack
LINKS
- App: https://bexo.app
- App Store: https://apps.apple.com/ar/app/bexo-wallet/id1533311061
- Play Store: https://play.google.com/store/apps/details?id=com.beexo&hl=en_US
- Social: Bexowallet
Doc with screenshot of traction: https://docs.google.com/document/d/1BdkCYN-ifh02KvSDtGC_DRLAhA7aN-mATAMpUWaHNAQ/edit?tab=t.0
Tranche #1 — Stellar Wallet MVP in Production
Total budget: $18,000
Completion date:
June 29, 2026
Timeline note:
This completion date is based on an assumed award start date of June 1, 2026. If the official SCF approval or award start date is earlier or later, Bexo will preserve the same delivery cadence and complete Tranche #1 approximately 4 weeks after the official award start date.
Brief description:
Tranche #1 delivers the first production-ready Stellar integration inside Bexo Wallet.
The goal of this milestone is to make Stellar USDC available as a native wallet network in the Bexo mobile app, using Bexo’s existing self-custody architecture and production infrastructure.
At the end of this tranche, users will be able to create or enable a Stellar account inside Bexo, hold Stellar USDC, view their balance and transaction history, receive USDC through their Stellar address/QR, and send Stellar USDC from the app using on-device signing.
This tranche does not include ARS ramps, QR merchant payments, NEAR Intents routing, Earn/yield, MoneyGram, SEP-31, regulated cross-border corridors, custom Soroban contract development, or any public release of Bexo’s proprietary source code. Those integrations are covered in later milestones or removed from the funded scope.
Bexo’s production codebase will remain private. Completion will be verified through the live app, TestFlight and/or Android Internal App Sharing where needed, controlled production-equivalent access, Stellar mainnet explorer links, transaction hashes, screenshots, technical documentation, QA evidence, and a short technical demo recording where appropriate.
Deliverable 1 — Stellar Account Support & Key Management
Budget: $7,000
Brief description:
Implement native Stellar account support inside Bexo’s existing wallet infrastructure.
Each eligible Bexo user will be able to enable a Stellar wallet linked to their existing Bexo identity. Stellar keypairs will follow Bexo’s existing self-custody model: private keys are generated and stored on the mobile device, while the backend stores only the user’s public Stellar address and non-sensitive account metadata.
The backend will not have access to user private keys and will not be able to move user funds without user authorization/signature.
How to measure completion:
- Stellar account support is available in the Bexo mobile app.
- Stellar appears as a supported network/account inside the user wallet experience.
- At least 5 Stellar mainnet accounts are created through the Bexo app flow or controlled production-equivalent flow.
- Public Stellar addresses are visible on Stellar mainnet explorer.
- Private keys remain on-device and are never sent to Bexo’s backend.
- Backend stores only public Stellar addresses and non-sensitive account metadata.
- Technical implementation note delivered, covering:
- Stellar account lifecycle.
- Key generation and storage model.
- Backend/mobile responsibilities.
- Error handling.
- Private key security boundaries.
- Evidence package delivered to reviewers, including screenshots, explorer links and implementation notes.
- Bexo’s proprietary production codebase remains private.
Deliverable 2 — Stellar USDC Support: Trustline, Balance, Receive Address and Transaction History
Budget: $5,500
Brief description:
Add Stellar USDC support to the Bexo app.
Users will be able to hold Stellar USDC, create or manage the required USDC trustline, view their Stellar USDC balance, display their Stellar receive address/QR, and see their Stellar transaction history inside the Bexo wallet experience.
This deliverable makes Stellar USDC usable as a native asset inside Bexo before adding more advanced flows such as ramps, QR merchant payments, NEAR Intents routing and Earn.
How to measure completion:
- Stellar USDC is available as an asset inside Bexo.
- USDC trustline creation is implemented and validated on Stellar mainnet or controlled production-equivalent flow.
- At least 5 Bexo-created Stellar accounts have USDC trustlines visible on Stellar explorer.
- Stellar USDC balance is displayed in the app.
- Stellar receive address and QR are displayed in the app.
- Stellar transaction history is fetched and shown in the app.
- Horizon integration is documented.
- Error states are handled for:
- Unfunded accounts.
- Missing trustline.
- Horizon/API failures.
- Empty transaction history.
- Unsupported or invalid destination addresses.
- Evidence package delivered to reviewers, including:
- Mainnet account addresses.
- Trustline explorer links.
- Screenshots from the app.
- Technical notes explaining the Horizon integration.
Deliverable 3 — Stellar USDC Send Flow with On-Device Signing
Budget: $5,500
Brief description:
Implement the first complete Stellar USDC payment flow inside Bexo.
A user will be able to send Stellar USDC to another Stellar address or to another Bexo user with a Stellar account. The transaction may be prepared with backend assistance, but the final signature happens on the mobile device. The backend submits and tracks the transaction status without access to the user’s private key.
This deliverable proves that Bexo can support self-custodial Stellar USDC payments in production.
How to measure completion:
- Successful Stellar USDC transfer between two Bexo-created Stellar accounts.
- Successful Stellar USDC transfer from a Bexo-created Stellar account to an external Stellar address.
- Transaction hashes included in the milestone report.
- Transactions visible on Stellar mainnet explorer.
- App shows pending, confirmed and failed transaction states.
- Backend persists transaction status and Stellar transaction hash.
- On-device signing flow documented.
- Internal QA checklist or automated tests covering:
- Address validation.
- Trustline validation.
- Transaction preparation.
- Transaction signing.
- Transaction submission.
- Failed transaction handling.
- Transaction status updates.
- Evidence package delivered to reviewers, including transaction hashes, screenshots, implementation notes and a short technical demo recording where appropriate.
Tranche #1 Completion Criteria:
Tranche #1 will be considered complete when Bexo has released the Stellar Wallet MVP in production or production-equivalent distribution, including:
- Stellar account support.
- On-device Stellar key management.
- Stellar USDC trustline support.
- Stellar USDC balance display.
- Stellar receive address and QR.
- Stellar transaction history.
- Stellar USDC send flow.
- Mainnet transaction tracking.
- Technical implementation documentation.
- Reviewer evidence package with screenshots, explorer links and transaction hashes.
This tranche does not include ARS ↔️ USDC ramps, QR merchant payments, NEAR Intents routing, Earn/yield, MoneyGram, SEP-31, regulated cross-border corridors, or custom Soroban contract development.
Bexo’s production source code will remain proprietary. Completion will be verified through the live app, TestFlight and/or Android Internal App Sharing where needed, controlled production-equivalent access, Stellar mainnet explorer links, transaction hashes, technical documentation, screenshots, QA evidence and a short technical demo recording where appropriate.
Tranche #2 — Stellar USDC Funding, Ramp and Argentine QR Payments
Total budget: $27,000
Completion date:
August 10, 2026
Timeline note:
This completion date is based on an assumed award start date of June 1, 2026. If the official SCF approval or award start date is earlier or later, Bexo will preserve the same delivery cadence and complete Tranche #2 approximately 10 weeks after the official award start date.
Brief description:
Tranche #2 expands the Stellar Wallet MVP delivered in Tranche #1 into Bexo’s existing funding and payment infrastructure.
The goal of this milestone is to connect Stellar USDC to practical Bexo use cases that already exist or are already supported by Bexo’s infrastructure:
1. ARS ↔️ Stellar USDC ramp bridge.
2. Stellar USDC top-up into Bexo custodial USDC balance.
3. Foreign users paying Argentine merchant QR codes from custodial USDC funded through Stellar.
4. Monitoring, reconciliation and operational hardening for these flows.
At the end of this tranche, Bexo users will be able to move between ARS and Stellar USDC, and eligible foreign users will be able to fund Bexo with Stellar USDC and pay Argentine QR merchants from their custodial USDC balance.
This tranche does not include NEAR Intents routing, Earn/yield, MoneyGram, SEP-31, regulated cross-border corridors, local payout providers in other countries, custom Soroban contract development, marketing, security audit costs, or public release of Bexo’s proprietary source code.
Bexo’s production codebase will remain private. Completion will be verified through production or production-equivalent flows, Stellar mainnet explorer links, transaction hashes, internal operation references, screenshots, technical documentation, QA evidence, monitoring evidence and short technical demo recordings where appropriate.
Deliverable 1 — ARS ↔️ Stellar USDC Ramp Bridge
Budget: $9,000
Brief description:
Connect Bexo’s existing ARS ↔️ USDC ramp infrastructure to Stellar accounts created inside Bexo.
Users will be able to buy Stellar USDC using ARS and sell Stellar USDC back into ARS through Bexo’s existing ramp flow. The user-facing experience should remain simple: users select ARS or USDC, confirm the operation, and Bexo handles the required Stellar settlement and internal ledger updates.
This deliverable focuses on making Stellar USDC usable within Bexo’s local currency flows, without requiring users to understand Stellar addresses, trustlines or blockchain-specific mechanics.
How to measure completion:
- ARS → Stellar USDC buy flow implemented.
- Stellar USDC → ARS sell flow implemented.
- At least 5 successful ARS → Stellar USDC operations completed through Bexo’s production or production-equivalent flow.
- At least 5 successful Stellar USDC → ARS operations completed through Bexo’s production or production-equivalent flow.
- Stellar transaction hashes included in the milestone report where the operation touches Stellar mainnet.
- Internal ramp operation IDs linked to Stellar transaction hashes or ledger movements.
- User balance updates correctly after each buy/sell operation.
- Backend persists operation status, Stellar transaction hash, amount, asset, user, provider/internal reference and final state.
- Error states handled for:
- Expired quotes.
- Insufficient balance.
- Failed Stellar transaction.
- Failed local settlement.
- Pending operation.
- Reconciliation mismatch.
- Reconciliation process documented for comparing:
- Bexo internal ledger.
- Stellar transaction state.
- Ramp provider/internal settlement state.
- Evidence package delivered to reviewers, including screenshots, sample operation IDs, Stellar explorer links where applicable, and technical implementation notes.
Deliverable 2 — Stellar USDC Top-Up for Foreign Users Paying Argentine QR Merchants
Budget: $10,000
Brief description:
Enable foreign Bexo users to fund their Bexo custodial USDC balance using Stellar USDC and use that balance to pay Argentine merchant QR codes.
This feature is designed for non-Argentine users visiting or operating in Argentina who hold USDC on Stellar and want to spend locally without needing an Argentine bank account, local wallet, or ARS balance.
The Stellar transaction is used as the funding rail: the user sends Stellar USDC to Bexo, and Bexo credits the user’s custodial USDC balance. QR payments are then executed from the user’s Bexo custodial USDC balance through Bexo’s existing Argentine QR payment infrastructure.
The merchant experience does not change. Argentine merchants continue receiving payments through the existing local QR payment rail in local currency. Merchants do not need to create a Stellar wallet, understand USDC, or complete additional onboarding.
This deliverable is not intended as a domestic Argentine-to-Argentine QR payment replacement. Its initial scope is specifically foreign users funding Bexo with Stellar USDC and using that balance to pay Argentine merchants.
How to measure completion:
- Foreign/non-Argentine user profile or eligibility logic defined for the QR payment flow.
- Stellar USDC deposit/top-up flow implemented for eligible foreign users.
- User’s Bexo custodial USDC balance is credited after a confirmed Stellar USDC deposit.
- Stellar deposit transaction hash is linked to the internal custodial balance credit.
- User can pay eligible Argentine merchant QR codes using the credited custodial USDC balance.
- At least 10 successful Argentine QR merchant payment operations completed by foreign-user profiles using custodial USDC funded through Stellar USDC.
- Each top-up operation links:
- User.
- Stellar source transaction hash.
- Stellar asset.
- Amount.
- Internal custodial balance credit reference.
- Final credit status.
- Each QR payment operation links:
- User.
- User country or eligibility profile.
- Argentine merchant/payment reference.
- Local QR payment reference.
- Custodial USDC debit reference.
- Final payment status.
- App shows clear states for the top-up flow:
- Waiting for Stellar deposit.
- Deposit detected.
- Confirming.
- Credited.
- Failed or requires review.
- App shows clear states for the QR payment flow:
- Preparing payment.
- Debiting custodial USDC balance.
- Processing local QR payment.
- Paid.
- Failed.
- Refunded or reversed where applicable.
- Backend implements idempotency to avoid duplicate balance credits and duplicate QR payments.
- Backend handles mismatch cases where:
- Stellar deposit is received but internal credit fails.
- Custodial USDC is debited but local QR payment fails.
- Local QR payment status remains pending.
- Technical documentation explains:
- Foreign-user eligibility logic.
- Stellar USDC deposit/top-up flow.
- Custodial USDC balance crediting.
- Argentine QR payment state machine.
- Local Argentine payment rail interaction.
- Failure and reconciliation handling.
- Evidence package delivered to reviewers, including screenshots, Stellar deposit transaction hashes, internal payment references, QR payment references, and a short technical demo recording where appropriate.
Deliverable 3 — Monitoring, Reconciliation and Payment State Hardening for Tranche #2 Flows
Budget: $8,000
Brief description:
Implement monitoring, reconciliation and operational hardening for the Tranche #2 flows: ARS ↔️ Stellar USDC ramp, Stellar USDC top-up, custodial USDC balance crediting, and Argentine QR payments.
This deliverable ensures that Stellar-related funding and payment operations are not only functional, but also observable and supportable in production.
How to measure completion:
- Monitoring implemented for:
- Stellar deposit detection failures.
- Stellar transaction submission failures.
- Pending or stuck Stellar transactions.
- Failed internal balance credits.
- Ramp operation mismatches.
- QR payment mismatches.
- Reconciliation process documented for:
- Bexo internal ledger.
- Stellar transaction state.
- Custodial USDC balance.
- Ramp operations.
- QR payment operations.
- Operational runbook delivered for support/debugging.
- Internal dashboards, logs or alerting evidence included in the reviewer evidence package.
- Failure scenarios documented with expected recovery path.
- Evidence package delivered with monitoring screenshots, reconciliation notes, alert examples where appropriate, and technical documentation.
Tranche #2 Completion Criteria:
Tranche #2 will be considered complete when Stellar USDC is connected to Bexo’s core funding and payment infrastructure beyond the basic wallet experience delivered in Tranche #1.
Completion requires:
- ARS ↔️ Stellar USDC ramp bridge implemented.
- Stellar USDC usable in buy/sell flows.
- Foreign-user Stellar USDC top-up flow implemented.
- Custodial USDC balance crediting from Stellar deposits implemented.
- Eligible foreign users can pay Argentine merchant QR codes from their custodial USDC balance.
- Monitoring and reconciliation implemented for Tranche #2 flows.
- Successful production or production-equivalent operations completed for ramp, top-up and QR flows.
- Stellar transaction hashes and/or settlement references linked to Bexo internal operation records where applicable.
- Reconciliation and error-handling documentation delivered.
- Evidence package delivered to reviewers.
This tranche does not include NEAR Intents routing, Earn/yield, MoneyGram, SEP-31, regulated cross-border corridors, local payout providers in other countries, custom Soroban contract development, marketing, security audit costs, or public release of Bexo’s proprietary source code.
Bexo’s production source code will remain proprietary. Completion will be verified through live or controlled production-equivalent flows, Stellar mainnet explorer links, transaction hashes, internal operation references, screenshots, technical documentation, QA evidence, monitoring evidence and short technical demo recordings where appropriate.
Tranche #3 — NEAR Intents, Simple Earn, Production Hardening and Mainnet Usage
Total budget: $36,000
Completion date:
September 21, 2026
Timeline note:
This completion date is based on an assumed award start date of June 1, 2026. If the official SCF approval or award start date is earlier or later, Bexo will preserve the same delivery cadence and complete Tranche #3 approximately 16 weeks after the official award start date.
Brief description:
Tranche #3 is the final production launch and hardening milestone for Bexo’s Stellar integration.
The goal of this milestone is to complete the production rollout of Stellar-powered Bexo features, extend Bexo’s existing NEAR Intents integration to support Stellar USDC routes where available, add a simple Stellar USDC Earn experience using existing Stellar/Soroban yield infrastructure where suitable, and deliver production monitoring, reconciliation and mainnet usage reporting.
This tranche focuses on turning the Stellar integration into a stable, production-ready user experience with clear observability, support processes and measurable adoption.
This tranche does not include MoneyGram, SEP-31, regulated cross-border corridors, local payout providers in other countries, custom Soroban contract development, deployment of a new lending protocol, guaranteed yield, marketing, security audit costs, or public release of Bexo’s proprietary source code.
Bexo’s production codebase will remain private. Completion will be verified through production app availability or controlled production-equivalent access, Stellar mainnet explorer links, transaction hashes, internal operation references, screenshots, technical documentation, monitoring evidence, QA evidence, final metrics report and short technical demo recordings where appropriate.
Deliverable 1 — NEAR Intents Extension for Stellar USDC Routes
Budget: $8,000
Brief description:
Extend Bexo’s existing NEAR Intents integration to support Stellar USDC as an additional source and/or destination asset for cross-chain routing, where supported routes are available.
Bexo already has NEAR Intents integrated. This deliverable is not a new third-party integration from scratch. The funded work focuses on adapting the existing routing flow to include Stellar USDC, validating available routes, showing quotes to users, handling user confirmation, tracking operation status and implementing fallback behavior when a Stellar route is not available.
This deliverable does not include building a custom bridge, deploying custom smart contracts, guaranteeing liquidity for every route, launching regulated cross-border corridors, or operating local payout infrastructure.
How to measure completion:
- Stellar USDC is added as a supported asset in Bexo’s existing NEAR Intents routing flow where routes are available.
- User can request a quote for at least one route involving Stellar USDC.
- User can confirm a Stellar USDC route from the Bexo app.
- Backend persists:
- User.
- Source asset.
- Destination asset.
- Source chain/network.
- Destination chain/network.
- Quote.
- Route provider.
- Operation status.
- Transaction hash or provider reference where applicable.
- App shows clear states:
- Quote requested.
- Route available.
- Route unavailable.
- Waiting for user confirmation.
- Submitted.
- Processing.
- Completed.
- Failed.
- Fallback behavior implemented when no Stellar USDC route is available.
- At least 3 successful controlled operations involving Stellar USDC are completed through the existing NEAR Intents flow, where supported by route availability.
- Evidence package delivered to reviewers, including screenshots, operation references, transaction hashes or provider references where applicable, and a short technical demo recording.
Deliverable 2 — Simple Stellar USDC Earn Integration / Readiness
Budget: $8,000
Brief description:
Implement a simple Earn experience for Stellar USDC inside Bexo.
The goal is to let eligible users access yield opportunities on Stellar without needing to understand DeFi, Soroban, liquidity pools or contract interactions.
Bexo will not build a new lending protocol, deploy a custom Soroban vault, or guarantee returns. The first version will integrate with existing Stellar/Soroban yield infrastructure, such as Blend Protocol where suitable, and expose it through a simple deposit / balance / withdraw user experience.
The APY will be shown as variable and not guaranteed. Users will receive clear risk and availability messaging before depositing.
If production deployment is not appropriate during the grant period due to protocol availability, liquidity, risk profile or technical constraints, Bexo will deliver production-equivalent readiness with technical documentation, test transactions, UX implementation and risk disclosures.
How to measure completion:
- Stellar USDC Earn screen implemented in Bexo.
- Eligible users can see whether Earn is available.
- App displays estimated variable APY where available.
- App includes clear risk disclosure:
- APY is variable.
- Yield is not guaranteed.
- External protocol risk exists.
- Funds are not bank deposits.
- Availability may change.
- Deposit flow implemented for Stellar USDC Earn, or production-equivalent technical flow completed.
- Earn position/balance display implemented.
- Withdraw flow implemented or production-equivalent technical flow completed.
- Backend persists Earn operation data:
- User.
- Asset.
- Amount.
- Operation type.
- Protocol/pool reference.
- Transaction hash or contract interaction reference where applicable.
- Operation status.
- Timestamp.
- App displays clear states:
- Available.
- Temporarily unavailable.
- Preparing deposit.
- Pending confirmation.
- Deposited.
- Preparing withdrawal.
- Withdraw completed.
- Failed.
- Technical documentation delivered explaining:
- Selected protocol/integration approach.
- Why no custom Soroban contract is required.
- Backend/mobile responsibilities.
- Transaction lifecycle.
- Risk assumptions.
- Failure handling.
- Monitoring and reconciliation.
- Evidence package delivered to reviewers, including screenshots, transaction or contract references where applicable, technical notes and a short demo recording.
This deliverable does not include custom Soroban protocol development, deployment of a new lending protocol, guaranteed yield, or investment advice.
Deliverable 3 — Production Release Hardening and UX Polish
Budget: $8,000
Brief description:
Harden the production user experience for all Stellar-related flows delivered across Tranches #1 and #2.
This includes improving reliability, edge-case handling, user-facing transaction states, error messages, support visibility, and the overall wallet/payment experience around Stellar USDC.
The goal is to ensure that the Stellar integration is usable by real users, not only technically functional.
How to measure completion:
- Stellar wallet UX finalized for production use.
- User-facing transaction states polished for:
- Stellar account creation.
- USDC trustline.
- Stellar USDC receive.
- Stellar USDC send.
- ARS ↔️ Stellar USDC ramp.
- Stellar USDC top-up.
- Custodial USDC balance crediting.
- QR payment funded from custodial USDC.
- NEAR Intents operations involving Stellar USDC.
- Earn flow where available.
- Clear user-facing errors implemented for:
- Invalid address.
- Missing trustline.
- Insufficient balance.
- Pending confirmation.
- Delayed deposit detection.
- Failed balance credit.
- Failed ramp operation.
- Failed QR payment.
- Route unavailable.
- Earn unavailable.
- Internal support/debugging metadata available for Stellar-related operations.
- QA checklist completed for supported flows.
- Screenshots and demo recordings delivered as part of the evidence package.
Deliverable 4 — Monitoring, Reconciliation, Analytics and Final Mainnet Usage Report
Budget: $12,000
Brief description:
Complete production-grade monitoring, reconciliation, analytics and final usage reporting for Bexo’s Stellar integration.
This deliverable ensures Bexo can operate the Stellar integration safely after launch, detect issues quickly, reconcile balances and transactions, support users when operations fail or remain pending, and provide reviewers with a clear view of Stellar adoption inside Bexo.
The budget is allocated to product analytics, internal reporting, data validation, production tracking, operational support for the launch period, monitoring, reconciliation and final documentation. It does not include marketing or promotional spend.
How to measure completion:
- Production analytics implemented for Stellar-related flows.
- Monitoring implemented for:
- Stellar account creation failures.
- Stellar transaction submission failures.
- Pending or stuck transactions.
- Horizon/API availability issues.
- Deposit detection failures.
- Balance crediting failures.
- Ramp reconciliation mismatches.
- QR payment mismatch cases.
- NEAR Intents route failures or stuck operations.
- Earn/Soroban operation failures where applicable.
- Reconciliation process documented for:
- Bexo internal ledger.
- Stellar mainnet transactions.
- Custodial USDC balances.
- Stellar USDC wallet balances.
- Ramp operations.
- QR payment operations.
- NEAR Intents operations.
- Earn operations where applicable.
- Operational runbook delivered, including:
- Common failure scenarios.
- Manual review process.
- Refund/reversal assumptions.
- Support debugging steps.
- Alert response flow.
- Known limitations.
- Final technical report delivered, including:
- Architecture updates.
- Production release summary.
- Known limitations.
- Security assumptions.
- Monitoring setup.
- Reconciliation process.
- Operational runbook.
- Screenshots.
- Representative transaction hashes.
- Internal operation references.
- Final adoption report delivered with measured results over the first 30 days after launch or controlled production rollout.
Target metrics:
- ≥300 Stellar wallets created through Bexo.
- ≥1,500 Stellar-related mainnet transactions or operations tracked by Bexo.
- ≥$60,000 in Stellar USDC volume processed through Bexo.
- ≥350 Argentine QR merchant payments completed by eligible foreign-user profiles funded through Stellar USDC top-ups.
- ≥3 successful Stellar USDC operations through Bexo’s existing NEAR Intents routing flow where route availability allows.
- Earn readiness completed, or Earn production flow available where protocol/liquidity/risk conditions are suitable.
If any metric depends on third-party route availability, liquidity, protocol conditions or app store review timing, Bexo will provide the actual measured result, explain the dependency, and provide verified technical evidence of production readiness.
Tranche #3 Completion Criteria:
Tranche #3 will be considered complete when Bexo has completed the final production launch or production-equivalent rollout of its Stellar integration and delivered a complete evidence package to reviewers.
Completion requires:
- Stellar wallet and Stellar USDC flows live in production or production-equivalent release.
- ARS ↔️ Stellar USDC ramp bridge available.
- Stellar USDC top-up flow available for eligible foreign users.
- Argentine QR merchant payment flow available using custodial USDC funded through Stellar USDC.
- Stellar USDC supported in Bexo’s existing NEAR Intents routing flow where routes are available.
- Simple Stellar USDC Earn integration or production-equivalent readiness completed using existing Stellar/Soroban yield infrastructure where suitable.
- Production UX hardening completed.
- Monitoring and alerting implemented for all Stellar-related flows.
- Reconciliation process documented.
- Operational runbook delivered.
- Final technical report delivered.
- Final adoption/metrics report delivered.
- Representative Stellar mainnet explorer links, transaction hashes, screenshots, operation references and demo recordings delivered where appropriate.
This tranche does not include MoneyGram, SEP-31, regulated cross-border corridors, local payout providers in other countries, marketing, security audit costs, custom Soroban protocol development, deployment of a new lending protocol, guaranteed yield, cross-border remittance corridors, or public release of Bexo’s proprietary source code.
Bexo’s production source code will remain proprietary. Completion will be verified through production app availability or controlled production-equivalent access, Stellar mainnet explorer links, transaction hashes, internal operation references, technical documentation, monitoring evidence, QA evidence, final metrics report and short technical demo recordings where appropriate.
We are a 3-person founding team that has shipped for 7 years fintech/crypto products with a B2B2C company, then built Bexo with everything they have learned:
Ezequiel Cuesta — CEO . Ex Xapo Bank Growth from 0 to Millions of transactions. His brother co-founded Xapo alongside Wenceslao Casares.
In fintech/crypto since 2013, building with purpose since then.
LinkedIn: https://www.linkedin.com/in/ezequielcuesta/
Santiago Iwakawa — CTO. Designed and shipped every project since 2019. The technical brain on behalf the best user experience on blockchain railways. Invented the alias-to-alias chat that allow users to send crypto like a message without long addresses.
LinkedIn: https://www.linkedin.com/in/siwakawa/
Juani Podesta — CGO / Product. Keynote speaker on fintech and stablecoins at events across Latin America. Deep expertise in user behavior in high-inflation economies.
LinkedIn: https://www.linkedin.com/in/juani-podesta-035b7416a/
siwakawa
Juani Podesta
No other submissions.