FAQ
Frequently asked questions about Amboss Payments — coverage, settlement, fees, supported assets, and webhook behavior.
Frequently asked questions about Amboss Payments.
What assets does it support?
USDT, USDC, and Bitcoin today, with more assets coming soon.
How fast are settlements?
Payments settle in seconds, 24/7/365. No batch processing, no banking hours.
How does it work under the hood?
Amboss uses the Lightning Network, the most battle-tested instant payment layer built on Bitcoin. You don't need to manage any of this infrastructure; our API abstracts it entirely.
Do I need to give up custody?
No. Amboss offers self-custodial options where you maintain full control of your keys.
What are the fees?
0.5% of payment volume plus a $30/mo base fee for managed node infrastructure. No hidden markups, no setup fees, no per-transaction flat charges.
How do I integrate?
A single GraphQL API at https://rails.amboss.tech/graphql. SDKs coming soon. Sign up at rails.amboss.tech and follow the Get Started sandbox-first walkthrough.
How do I send payments?
Use the create_send mutation with either a BOLT11 invoice (request.bolt11) or a Lightning Address (address.lightning_address + amount). See Send Payments.
How do I receive payments?
Use create_receive to mint a BOLT11 invoice, then listen for the payment.completed webhook. See Receive Payments and Webhooks.
Which auth header does Payments use?
x-api-key: <key>. The other Amboss products use Authorization: Bearer <key>. See Developer → Authentication for the per-product table.