Developer Platform overview
Build apps that merchants install on spuke.
What you can build
The spuke Developer Platform lets you ship software that merchants install into their spuke account. Apps read payment data, react to events in real time and can be sold in the spuke App Store.
| Building block | What it gives you |
|---|---|
| App | Your listing, credentials and install lifecycle |
| App API | REST access to a merchant's spuke resources, scoped by consent |
| Webhooks | Signed, retried event delivery to your backend |
| Environments | Isolated sandbox merchants for end-to-end testing |
| Monetization | Free, one-time or subscription pricing in EUR |
The lifecycle
- Create a developer account and complete verification.
- Create an app — it receives an 8-digit app number and a draft listing.
- Build against a sandbox environment with test merchants.
- Submit the app for review.
- Publish. Merchants install it from the spuke App Store.
Every app starts in test mode. Live credentials are only issued after review and payout verification.
Two modes, always separated
| Test (sandbox) | Live | |
|---|---|---|
| Credentials | test client id / secret |
live client id / secret |
| Data | Sandbox merchants you own | Real merchants who installed you |
| Money | Simulated ledger | Real payouts |
| Rate limits | Counted separately | Counted separately |
A token minted in one mode can never read the other mode's data.
What an app is not
Apps are not a PSP integration. You never touch card data, never hold funds and never call the acquirer. spuke stays the merchant of the payment relationship; your app works on top of it.