Going Live

You build and test against staging. When you’re ready, we switch you to production: a different host with its own credentials.

	Staging	Production
Base URL	`https://edpay-dotnet-api-staging.edubanc.ng`	Shared by EdPay when you go live
API key / secret	Issued on signup	Issued separately for production
Money moves	No	Yes: real loans and disbursements

Staging keys do not work in production, and vice versa. Keep them in separate environment configs.

Pre-launch checklist

All calls to EdPay are made from your servers, never a browser or mobile app
API secret is stored in a secrets manager, not in source control
Base URL, key, and secret come from environment config, so switching is a config change
Schools, bank accounts, and tuition fees sync correctly using your own externalSchoolId / externalStudentId
You handle the response envelope, check success and surface errors on failure
Loan status is shown from GET .../loans and you handle every status (Submitted → Disbursed → Active → Closed, plus Rejected and Cancelled)
If you embed the parent flow: SSO sessions are created per parent and the full journey (BVN → assessment → application → mandate) works end to end
Network errors and 5xx responses are retried safely, writes are idempotent

Request production access

Email hello@edubanc.ng with the subject “EdPay go-live request” and include:

Your company name and the technical contact from your original request
Confirmation that you’ve completed the checklist above
A short walkthrough of your integration (a demo call or screen recording works)
Your expected launch date and initial number of schools

We’ll review the integration, then send you your production base URL, API key, and secret. Swap them into your environment config and you’re live.

After launch

Start small. Onboard a pilot school first and watch a few loans through to disbursement.
Monitor. Log the statusCode and errors from every failed call.
Talk to us. Reach hello@edubanc.ng any time, support issues, key rotation, or new features.