Overview
Loading your company
Signatures per day
UsageTable of values
| Day | Coin sends | Token sends | Speed-ups | Cancels | Total |
|---|
No signatures yet this month
Every coin send, token send, speed-up and cancel the Wallet signs with your keys is counted here by day.
See the quick startWhat is stopped and what still works
- API keys
- Every request with a key fails with the stopped-service error. The keys are not revoked.Stopped
- Event stream
- Wallet events 3.0No events are delivered; the position is kept.Stopped
- Mode B sends
- Your siteYour site's users get
CLIENT_SERVICE_STOPPEDwhen they try to send.Stopped - Webhooks
- Your webhookDeliveries continue from where they paused when the month is paid. The 3-day log keeps counting from then.Paused
- Mode B sign-in and balances
- Your siteUsers sign in and see their balances as usual.Working
- Cabinet
- Statements, usage, keysEverything stays readable; Usage shows the month at zero.Working
Statement, estimate
Talk to us
Change plan, pay for a month, or ask a question. We answer in the cabinet.
Quick start
Your backend holds the key and creates, sends and tracks wallets. Keys never leave hardware isolation.
curl -H "Authorization: Service $SHUTTLE_KEY" https://api.shuttle.technology/v1/service/walletsYour users sign in on your site and come back to a return URL you listed under Allowed URLs. A sign-in that returns to an address not on the list does not pass.
Your service forwards sends on behalf of users. The signature is billed to you.