Environments
Configure environments, API base URLs, and authentication with client-id and client-secret.
JGME Pay runs a single live environment:
| Environment | Use Case | API Base URL | Dashboard |
|---|---|---|---|
| Production | Live transactions | https://api.jgmepay.com | https://merchant.jgmepay.com |
Every request moves real money. Develop against the smallest amount your providers accept, and keep your credentials out of client-side code.
API Authentication
All API calls require these headers:
client-idclient-secret
You can find both in:
Dashboard -> Settings -> Security -> API Keys and Webhooks
Example Request
curl --location 'https://api.jgmepay.com/payments/v1/checkouts' \
--header 'client-id: <your-client-id>' \
--header 'client-secret: <your-client-secret>' \
--header 'Content-Type: application/json' \
--data '{
"reference": "test-001",
"amount": 1000,
"currency": "NGN",
"country": "NG",
"user": {
"phoneNumber": "08012345678"
}
}'Production Go-Live Checklist
Validate your integration
Validate successful, failed, and pending flows, including webhooks, using the smallest amounts your providers accept.
Confirm credentials and base URL
Confirm your live client-id/client-secret are in place and your API base URL is https://api.jgmepay.com.
Verify webhooks in production
Confirm your production webhook URL is configured under Settings -> Security -> API Keys and Webhooks.
Recommended App Configuration
Use environment variables so secrets stay out of source code:
JGME_PAY_BASE_URL=https://api.jgmepay.com
JGME_PAY_CLIENT_ID=...
JGME_PAY_CLIENT_SECRET=...const config = {
baseUrl: process.env.JGME_PAY_BASE_URL,
clientId: process.env.JGME_PAY_CLIENT_ID,
clientSecret: process.env.JGME_PAY_CLIENT_SECRET,
};Security Notes
- Never expose
client-secretin frontend apps. - Never commit credentials to git.
- Rotate keys immediately if you suspect exposure.
- Use HTTPS for API and webhook endpoints.