Test in the sandbox
Generate your test key in the dashboard and validate Pix, balances and webhooks with simulated funds.
Accept Pix, hold a balance in Brazilian reais and choose when to withdraw in Pix or crypto. One API connects your software to payment providers.
Test without real funds No fixed wallet required for BRL custody
Prefer a conversation? Talk to a person on WhatsApp ↗
Collections, balances and payouts connected through one API. Choose the flow that fits your product.
Receive the net amount in BRL custody, organize balances by customer and choose when to pay or withdraw.
No fixed wallet at collection. Choose the network and address when withdrawing crypto.
Explore BRL custody →Your customer makes a regular Pix payment. Lunium detects it, converts the funds and settles the stablecoin to the configured address.
Check the API catalog for assets, networks, minimums and estimates.
Explore cash-in →Send USDT or USDC. Get a quote, accept the order and deposit the stablecoin. Lunium then executes the Pix settlement.
Available on multiple networks, as listed in the API catalog.
Explore cash-out →Send Pix directly from your software through Lunium’s infrastructure. Create payments, track their status and reconcile every operation through the API.
Pay in Brazilian reais, directly to the recipient’s Pix key.
Explore payouts →Funds can remain in BRL custody. Organize balances by customer and decide how to use the available amount, without setting a crypto wallet at collection.
Explore BRL custodyCheck assets, networks, fees and limits through the API before each operation.
Illustrative flow · use of available funds
Create your account, open the partner dashboard and test your integration. When ready, create a separate production key in the same account.
Generate your test key in the dashboard and validate Pix, balances and webhooks with simulated funds.
Complete your business details and generate the production key. Credentials and operations remain separate from sandbox.
The infrastructure lets developers start with the API, with no sales meeting required.
POST /keys/sandboxPOST /cashin/previewPOST /cashin/chargecashin.settledNo manual credential provisioning. No waiting for someone to create your first key.
Standard integration: 2% + R$ 2.00 per operation. Volume partners negotiate their rate, down to 35 bps over the USDT market reference price for exclusive partners. No monthly fee: your key's current rate is returned by GET /keys/me and every quote is already net of fees.
const response = await fetch(
"https://api.luniumpay.com/cashin/charge",
{
method: "POST",
headers: {
"X-API-Key": process.env.LUNIUM_API_KEY,
"Content-Type": "application/json"
},
body: JSON.stringify({
amount_cents: 25000,
payer_tax_number: "12345678901",
payout_address: "0x…",
asset: "usdt",
external_id: "order_8812"
})
}
);
const charge = await response.json();
{
"cashin_id": "ci_b3f9d2a41c6e…",
"status": "pending",
"amount_cents": 25000,
"chain": "polygon",
"asset": "usdt",
"qr_copypaste": "00020126…",
"qr_image_url": "https://…",
"external_id": "order_8812",
"expires_at": "2026-…"
}
Your application receives the Pix payment. Lunium handles the rest of the flow.
From ChatGPT to Fable, give your AI the API context and an integration path. Your team can also start directly with code.
A REST API, OpenAPI 3.1, a deterministic sandbox and production. Existing integrations keep working as before.
Start buildingOpen discovery standards, a machine-readable capability catalog, integrator-defined spending policies and rule-based production activation.
Lunium for agentsSandbox, OpenAPI and MCP. Discovery, implementation, testing and production activation, subject to your authorization and the API’s requirements.
Follow operations in the partner portal and your account-scoped monitor. Build live tracking into your product with webhooks and status queries.
From online sales to supplier payments, find the Lunium flow that fits your operation.
Connect your BRL cash flow to stablecoin payments for counterparties that accept this settlement method.
Add Pix collection, customer balances and Pix or crypto withdrawals to the product you are building.
Collect with Pix, identify each customer and update your software when payment is confirmed.
Bring Pix into your checkout, reconcile orders and choose where your received balance goes.
Explore how operations work. Catalogs, fees, states, testing and failure recovery, organized for you and your team.
Aligned with the production API and checked against it.
Import the API specification and start testing immediately.
Verify the authenticity of every event using its cryptographic signature.
Retry operations safely without creating duplicate financial transactions.
Build predictable error handling instead of interpreting free-text messages.
Discover available assets and networks programmatically instead of hard-coding them.
Use API responses and settlement identifiers as the financial source of truth.
Lunium’s catalog exposes the assets and networks currently available for cash-out.
GET /catalog
Availability changes. Your integration does not have to guess — check the catalog before offering a route.
Financial infrastructure should never make your application guess the final amount.
POST /cashin/preview
Get a quote without creating a charge, with your key’s fee already applied.
POST /cash-outs
A quote with an explicit expiry. Nothing executes until you accept it.
The API returns the amounts used by the transaction.
Your system displays the quote. Lunium remains the source of truth.
Actual contract states: the Pix reaches paid; on-chain delivery is tracked by settlement_status (pending → sending → sent) and the cashin.settled event signals when to credit the delivery.
Internal conversion states map to a single event: cashout.processing — you do not need to handle each internal state.
Your application tracks state through the API and receives each transition by webhook.
Financial APIs need careful failure handling.
Connections drop. Servers restart. Responses time out.
And your application retries the request.
Lunium’s idempotency model lets the same external_id safely reference the same financial operation, including to recover it after an ambiguous error.
api.luniumpay.com
Use Lunium’s API to create, track and reconcile operations programmatically.
An API for software. An assistant for people.
Test Pix collections, BRL custody, crypto withdrawals, Pix payouts and internal transfers with simulated funds. Sandbox reproduces integration states without paying real Pix or moving real crypto. For cash-out, the scenarios below cover success, delays and failure.
POST /keys/sandbox
Create a test credential without moving real funds — one API call.
Read the current configuration directly from the API.
GET /keys/meAccount configuration, current limits and eligibility in a machine-readable response.GET /catalogCurrently available assets and networks.GET /cashin/chargesCash-in history.GET /cash-outsCash-out history.GET /payoutsPayout history.Your integration reads the current configuration instead of relying on assumptions.
Explore the documentation and test the API before discussing your production needs with our team.
Then talk to us when you need production limits, commercial terms or enterprise support.
Start in sandbox. Test the flow. Take your integration to production.
Pix · BRL custody · Crypto · Payouts
Choose your product’s flow or explore the integration resources.
Short, verifiable answers. Full details are in the FAQ and the documentation.
Your application calls POST /cashin/charge and receives a Pix QR code and copy-and-paste payload for the payer. Once Pix is paid, crypto settlement delivers USDT or USDC. Track payment and settlement states through GET /cashin/{id}/status and signed webhooks.
Use cash-out: POST /cash-outs/preview returns a quote; POST /cash-outs creates the order; POST /cash-outs/{id}/accept returns the deposit address. Once the USDT or USDC deposit is confirmed, the Pix payout is sent to the specified key.
In the dashboard, create an account to manage sandbox and production keys together. Direct API access remains available: POST /keys/sandbox with your email creates a test key in one call, without a dashboard account. AI agents can continue through Mesh or MCP. It simulates Pix to custody or crypto, Pix and crypto withdrawals, internal transfers and crypto to Pix. It includes states, failures and webhooks. Funds are simulated and the Pix QR code is non-payable; real payments require production. The email is required because that is where we send the manual, the flowchart and the integration steps.
Check GET /cashin/catalog to receive crypto after a Pix payment, and GET /catalog to deposit crypto and receive Pix. USDT, USDC and other assets depend on the flow, network and current availability. The two directions use different catalogs; confirm the route before offering it.
CPF, CNPJ, phone number, email or random Pix key. The API validates the format. Optional recipient lookup may be unavailable; check the returned result and recipient details.
Yes. GET /v1/verificar/{e2e} is a public endpoint: anyone with the Pix end-to-end identifier can check whether a payment settled, without an API key.
There is no monthly fee: pricing is per operation. GET /keys/me returns the current fee for your key, and quotes include the net amount. See luniumpay.com/en/faq for details.
ZANQUETA INTERMED LTDA, CNPJ 68.538.127/0001-00. Contact: contato@luniumpay.com.
A test key takes one API call, with no prior approval. If that is what you need, start with the documentation. Use this form for volume pricing, a case the docs do not cover or a question before integrating.
Prefer email? contato@luniumpay.com