Going live

Ready to take real payments? Here's what to verify before flipping the switch.

Pre-launch checklist

Walk through this list before pushing your live key to production:

• ☐ Wallet address configured and verified with a test deposit
• ☐ Live API key created and stored in a secret manager (not git)
• ☐ Live webhook endpoint registered with HTTPS
• ☐ Webhook signature verification implemented and tested
• ☐ Idempotency on order fulfillment (use event.id to dedupe)
• ☐ Error handling for declined cards, 3DS abandonment, expired sessions
• ☐ Monitoring set up for failed webhook deliveries
• ☐ Customer support email or chat for refund/dispute requests
• ☐ Refund policy published on your site
• ☐ Terms of service and privacy policy that mention card payments

Environment variables

Your production environment should have:

SKIRO_API_KEY=sk_live_...
SKIRO_WEBHOOK_SECRET=whsec_...

Use a secret manager (Vercel Environment Variables, AWS Secrets Manager, Doppler, 1Password): not .env files committed to git.

Your first real payment

Process a small real transaction yourself to verify everything works:

1. Use one of your own cards. Charge $1 or whatever the smallest amount makes sense.
2. Watch the transaction appear in Transactions.
3. Verify the payout lands in your wallet within ~5 minutes.
4. Check the webhook fired and your handler ran.
5. Confirm your customer-facing flow worked end-to-end.

If anything looks off, refund yourself and debug before opening to real customers.

Monitoring

Things to watch in your first week:

• Webhook delivery success rate. The dashboard shows this. Aim for >99%.
• Transaction conversion rate. Sessions created vs sessions completed. Below 80% suggests checkout friction.
• Decline rate. If too high, you may be attracting fraud. Tighten your fraud rules.
• Average payout time. Should be under 5 minutes. If it spikes, check the chain's status.

Scaling tips

As volume grows:

• Upgrade to Pro or Business to lower your per-transaction fee: see pricing.
• Move webhook processing to a queue. Don't block the response on long tasks.
• Cache common API responses (your own merchant info, fee rates).
• Consider multiple wallet addresses to spread risk: contact us for multi-wallet routing on Business and Enterprise plans.

That's it. Welcome to the Skiro merchant club.