befetti
[ 200 OK ]
[ REWARDS ]
[ .JSON ]
[ .MD ]
Design partners open — Q3 2026

Ship Bitcoin rewards to your users.Not seed phrases.

Rain sats on your users — rewards that feel like confetti, not paperwork.

Embed non-custodial Bitcoin wallets into your app. Send sats or custom loyalty assets with one API call. We handle VTXO lifecycle, refresh, and fraud controls so your users keep what they earn — and you never touch custody.

Get early access
See how it works
Not a bank· Not a custodian· Not a money transmitter

Built on Ark protocol · Non-custodial by design · Testnet Q3 2026

One API call. One reward. Zero wallet infrastructure.

Your backend calls Befetti. A VTXO is issued and routed to the user's on-device wallet. The reward lands in-app. That's the whole integration — under 15 lines, no backend infra to stand up.

~/befetti-demo
import { Befetti } from '@befetti/sdk';

const befetti = new Befetti(process.env.BEFETTI_SECRET_KEY);

await befetti.rewards.send({
  userId: 'player_9f2a',
  asset: 'sats',
  amount: 25,
  campaignId: 'match_win',
  idempotencyKey: 'evt_a8f2c1',
});

Idempotent by default. Retryable. Returns a signed VTXO receipt.

Reward flow

01
Your Backend
POST /v1/rewards
02
Befetti
VTXO issued & routed
03
User Wallet
Sats land in-app

Everything you need. Nothing you don't.

App-native, non-custodial wallets

Passkey-first user creation. No seed phrases. Your users never install a separate wallet app. You never touch their keys.

Rewards API, built like Stripe

Idempotent. Batched. Rate-limited. Campaign-scoped. Send sats or custom Arkade assets with one call.

VTXO lifecycle, fully managed

Designed to prevent expiry-driven fund loss: we watch every VTXO timelock and refresh on-chain before it lapses, so rewards stay claimable.

From zero to first reward in under a day

01

Grab an API key

Sign up. Create a project. Get a testnet API key. Two minutes.

02

Drop in the SDK

Fifteen lines of JavaScript. A wallet appears in your app, protected by the user's device passkey.

03

Send your first reward

One POST /v1/rewards from your backend. The reward lands in the user's wallet in seconds.

04

We handle the rest

VTXO refresh, expiry alerts, dashboard, fraud controls, cashout partner routing. You focus on your app.

See a live integration

Built for consumer apps that reward their users

Games

Reward players with sats for wins, achievements, and daily play. Build native in-game economies with custom Arkade assets.

Creator platforms

Tip creators. Reward fans. Distribute community currency. All in-app, no wallet detour.

Education

Pay learners for course completion. Prove engagement. Retain users past week one.

Loyalty

Replace points systems with real, portable Bitcoin-native rewards. Users own their balance.

The three options developers have today. And why they all break down.

User ownership
Points DB — Points belong to you
Third-party custodial — Provider holds custody of user funds
Befetti — Full — non-custodial, invisible to user
Time to integrate
Points DB — Weeks
Third-party custodial — Days
Befetti — Half a day
Wallet UX
Points DB — You build it
Third-party custodial — Branded third-party wallet app required for cashout
Befetti — Drop-in, passkey-first, in-app
Lifecycle management
Points DB — N/A
Third-party custodial — Managed by the provider
Befetti — Fully managed (VTXO refresh, expiry, alerts)
Regulatory posture
Points DB — You're the issuer + custodian
Third-party custodial — Provider is the custodian & MSB
Befetti — Software / infrastructure
Custom loyalty assets
Points DB — Points only, closed-loop
Third-party custodial — Sats only
Befetti — Sats + custom Arkade assets, one API call
Cashout
Points DB — You build it or partner
Third-party custodial — Via the provider's wallet only
Befetti — Partner-routed, jurisdiction-aware

Befetti sits on top of Ark protocol. We handle everything that isn't the protocol.

Built on the protocols developers trust

Ark protocol
Second-layer Bitcoin scaling
Arkade Assets
Bitcoin-native custom asset issuance
WebAuthn / Passkeys
OS-level biometric authentication
Non-custodial by design
Users control keys, always
Custody
Can Befetti move user funds?
No. In non-custodial mode, funds require the user's device passkey or key material. Befetti has no unilateral spend authority.
Is this testnet or mainnet?
Testnet at launch. Mainnet controlled beta after design partner pilots.
Integration
What platforms does the SDK support?
JavaScript at MVP. React Native, iOS, Android, and Unity on the roadmap.
How is Befetti different from Second (bark)?
Second builds the Ark wallet protocol layer. Befetti builds the developer platform on top: reward APIs, campaigns, lifecycle orchestration, dashboards, and multi-tenant infra.

Under the hood

How it stays non-custodial — the questions sharp devs ask first

Where are the keys stored?

On the user's device secure enclave (Apple Secure Enclave / Android StrongBox), gated by passkey or biometric. No seed phrases are shown to the user, and the key material never touches Befetti servers.

What if the user loses their device?

Recovery uses passkey sync (iCloud Keychain, Google Password Manager) as the primary path. Design partners can additionally opt into an encrypted key-backup flow — Befetti holds only the ciphertext, and the user's passkey holds the unlock.

Can users exit without Befetti's servers?

Yes. Every VTXO carries an on-chain unilateral exit path within its timelock. If Befetti disappears, users can broadcast the exit tx and settle to their own on-chain address.

What happens if Befetti goes down?

Users retain the ability to exit on-chain — funds are never held by us. Rewards already delivered remain the user's property; only new issuance from your account pauses until service is restored.

Security & openness. How we keep it safe.

Security
  • Third-party audit scheduled before mainnet beta.
  • Public bug-bounty program at mainnet launch.
  • Coordinated disclosure: security@befetti.com
Open source

SDKs and reference integrations ship in the open under the Befetti GitHub org.

github.com/befetti

Where we are

Status & timeline

We're pre-launch. Here's exactly what exists today, what ships next, and which platforms are in flight — so you can decide whether now is the right time to plug us in.

TestnetQ3 2026
MainnetControlled beta after pilot
SDKJavaScript at MVP → React Native, iOS, Android, Unity

Early access · Q3 2026

Be one of the first apps to ship Bitcoin rewards.

Join the waitlist

Get launch updates and early SDK access. One email. No spam.

Keys never leave the device Non-custodial by design

We'll reply within 48 hours. No spam. Ever.

Apply as a design partner

First 20 apps get early SDK access, hands-on integration support, and preferred pricing.

We'll reply within 48 hours. No spam. Ever.