Getting Started

Going Live

Production readiness checklist for launching your Elebne integration with live keys.

Going Live

Before switching from sandbox to production, work through this checklist to make sure your integration is ready for real transactions.

Pre-launch checklist

Test your integration thoroughly

All payment flows work in sandbox (create, pay, refund)
Webhook endpoints receive and process events correctly
Edge cases tested with magic amounts (99901 for payment failure, 99904 for refund failure)
Error responses handled gracefully in your UI

Secure your integration

Webhook signature verification is implemented and tested
Secret keys (sk_) are stored in environment variables, never in client code
Idempotency keys are sent on all write requests
IP allowlist configured for production keys (recommended)

Handle failures

Retry logic handles network timeouts and 5xx errors
Webhook handler processes events idempotently (duplicate events do not cause duplicate actions)
User-facing error messages are clear and helpful

Request live access

Apply for live keys

Open the Elebne mobile app, go to Commerce > Developer, and tap Request Live Access. Your application will be reviewed by the Elebne team.

Wait for approval

The review typically takes 1-2 business days. You will receive a notification in the app when your live keys are ready.

Receive your live keys

Once approved, you will see pk_live_ and sk_live_ keys in Commerce > Developer. These keys operate on real funds.

Update your integration

Replace your test keys with live keys in your server configuration. Your code should not need any other changes — the API endpoints and behavior are identical.

# Environment variables
ELEBNE_PUBLIC_KEY=pk_live_YOUR_KEY
ELEBNE_SECRET_KEY=sk_live_YOUR_KEY

Update webhook endpoints

If your webhook URLs differ between staging and production, register new endpoints with your production URLs:

curl -X POST https://api.elebne.ai/api/v1/dev/webhooks/endpoints \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "X-Idempotency-Key: prod-webhook-$(date +%s)" \
  -d '{
    "url": "https://your-production-server.com/webhooks/elebne",
    "events": ["payment.confirmed", "order.new"]
  }'

Monitor your first transactions

Watch the first few live transactions closely. Check that:

Payments complete successfully
Webhooks are delivered and processed
Amounts and commissions are correct
Settlement appears in your Elebne Commerce balance

Common gotchas

Do not mix test and live keys

Test keys and live keys operate in separate environments. A payment intent created with sk_test_ cannot be retrieved with pk_live_, and vice versa.

Webhook secrets are different per endpoint. If you register a new production webhook endpoint, it gets a new secret. Update your verification code accordingly.
Sandbox data does not carry over. Products, orders, and payment intents from sandbox mode are not visible in production.
Commission is 2%. Factor this into your pricing. On a 500.00 MRU payment, you receive 490.00 MRU.

Next steps

Environments — Full comparison of sandbox and production
Authentication — Key management and rotation
Webhooks — Ensure your webhook handling is production-ready

Was this page helpful?

Common Patterns

Response formats, required headers, amounts, dates, phone numbers, pagination, and other conventions used across the Elebne API.

Environments

Comparison of sandbox and production environments in the Elebne Developer API.

Going Live

On this page