Open Banking Gateway

Built for the next connection

Banking integrations, one clear starting point.

Explore wallet and banking workflows before connecting real accounts. One gateway, explicit access, and a sandbox for every integration.

  • Test with fixtures, not real funds
  • Live access clearly labeled
  • Pay only for successful live calls
Explore the APIsIntegration guide
1,000 welcome credits · no card
A safe first requestSandbox
Request · POST
curl -X POST 'https://www.openbankinggateway.com/api/sandbox/bkash-agent/login/request-otp' \
  -H 'Content-Type: application/json' \
  --data '{
  "account": "01700000001",
  "phoneOperator": "Grameenphone"
}'
Example responseX-Credits-Charged: 0
{
  "code": 200,
  "data": {
    "statusCode": "0000",
    "newCustomer": false,
    "success": true
  }
}

Illustrative sandbox example. No provider is contacted, no SMS is sent, no funds move, and no credits are charged.

The integration library

Find your next integration.

Every API includes endpoint references and a free sandbox. The availability badge tells you what can connect to real accounts today.

All APIs

Keep exploration, account access, and billing separate.

From first request to live connection.

  1. Explore without signing in

    Choose an API and use its sandbox with the documented test values. Fixtures do not move money or contact a bank.

  2. Create your gateway account

    Sign in with Google for 1,000 welcome credits and create an API key. This signs you into the website, not a wallet.

  3. Connect when you are ready

    For a supported live API, complete the wallet login separately. Successful live requests cost one credit; failed requests cost none.

Clear boundaries, before your first request.

A few things worth knowing.

Does the sandbox use real accounts?

No. Sandbox responses are fixtures and use public test credentials. They do not contact a financial provider, send an OTP, or move funds.

Can every API make live requests?

No. Only integrations marked as live have a real upstream. All others are sandbox-only and return LIVE_ACCESS_NOT_ENABLED in live mode. Contact us to discuss access.

When is a credit charged?

One credit is charged for a successful live call. Failed calls and sandbox calls are free. Check X-Credits-Charged rather than HTTP status alone. If X-OBG-Settlement: unknown is present, billing is unresolved: X-Credits-Charged: 0 does not prove that no debit occurred. Check usage and reconcile before retrying.

Does Google sign-in connect my wallet?

No. Google sign-in manages your site account, credits, and API keys. Wallet login is a separate, explicit flow for a supported integration and an account you are authorized to use.

Make your first request a sandbox request.

Explore the contract now. Add live access only when your integration is ready.

Explore the APIs