Open Banking Gateway
Sandbox only

Merchant banking · India

slice Business API

slice Business merchant banking (India) — OTP login, profile & balance, collection/passbook ledgers, beneficiaries, and two-step bank transfer.

9 endpointsFree sandbox

Sandbox · Request

curl · POST /login/start
curl -X POST 'https://www.openbankinggateway.com/api/sandbox/slice/login/start' \
  -H 'Content-Type: application/json' \
  --data '{
  "phone": "9000000000",
  "pin": "0000"
}'

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

API reference

Know what you can call.

Methods, paths, and parameter rules come from the same catalog that powers the console. Open an endpoint to see its request fields.

Wallet authentication

POST
/login/start

Start the OTP login

Sandbox only

/api/sandbox/slice/login/start

POST login/start · Parameter
ParameterTypeRules & handling
phoneRequiredstring

JSON body

Use a wallet you are authorized to access. Live identities must be linked to your site account through wallet login.

  • Format: ^[6-9]\d{9}$
pinRequiredstring

JSON body

Sensitive · never put in URLs

  • Format: ^\d{4,6}$
POST
/login/confirm

Confirm the OTP and issue a session token

Sandbox only

/api/sandbox/slice/login/confirm

POST login/confirm · Parameter
ParameterTypeRules & handling
phoneRequiredstring

JSON body

Use a wallet you are authorized to access. Live identities must be linked to your site account through wallet login.

  • Format: ^[6-9]\d{9}$
otpRequiredstring

JSON body

Sensitive · never put in URLs

  • Format: ^\d{4,8}$

Account & activity

GET
/profile

Merchant profile

Sandbox only

/api/sandbox/slice/profile

GET profile · Parameter
ParameterTypeRules & handling
tokenRequiredstring

Send in X-OBG-Token

Session token from the login step. Prefer the X-OBG-Token header so it stays out of URLs.

Sensitive · never put in URLs

  • Format: ^[A-Za-z0-9._~+/=-]{8,512}$
GET
/account-screen

Balance and bank account summary

Sandbox only

/api/sandbox/slice/account-screen

GET account-screen · Parameter
ParameterTypeRules & handling
tokenRequiredstring

Send in X-OBG-Token

Session token from the login step. Prefer the X-OBG-Token header so it stays out of URLs.

Sensitive · never put in URLs

  • Format: ^[A-Za-z0-9._~+/=-]{8,512}$
GET
/transactions

Recent QR/UPI collections

Sandbox only

/api/sandbox/slice/transactions

GET transactions · Parameter
ParameterTypeRules & handling
tokenRequiredstring

Send in X-OBG-Token

Session token from the login step. Prefer the X-OBG-Token header so it stays out of URLs.

Sensitive · never put in URLs

  • Format: ^[A-Za-z0-9._~+/=-]{8,512}$
pageNumberOptionalinteger

Query parameter

  • Range: 0 … 1000
pageSizeOptionalinteger

Query parameter

  • Range: 1 … 100
GET
/passbook

Bank passbook ledger (CREDIT/DEBIT)

Sandbox only

/api/sandbox/slice/passbook

GET passbook · Parameter
ParameterTypeRules & handling
tokenRequiredstring

Send in X-OBG-Token

Session token from the login step. Prefer the X-OBG-Token header so it stays out of URLs.

Sensitive · never put in URLs

  • Format: ^[A-Za-z0-9._~+/=-]{8,512}$
pageNumberOptionalinteger

Query parameter

  • Range: 0 … 1000
pageSizeOptionalinteger

Query parameter

  • Range: 1 … 100

Transfers

GET
/beneficiary/manage

List saved beneficiaries

Sandbox only

/api/sandbox/slice/beneficiary/manage

GET beneficiary/manage · Parameter
ParameterTypeRules & handling
tokenRequiredstring

Send in X-OBG-Token

Session token from the login step. Prefer the X-OBG-Token header so it stays out of URLs.

Sensitive · never put in URLs

  • Format: ^[A-Za-z0-9._~+/=-]{8,512}$
POST
/sendMoney/prepare

Prepare a bank transfer (sends a confirmation OTP)

Sandbox only

/api/sandbox/slice/sendMoney/prepare

POST sendMoney/prepare · Parameter
ParameterTypeRules & handling
tokenRequiredstring

Send in X-OBG-Token

Session token from the login step. Prefer the X-OBG-Token header so it stays out of URLs.

Sensitive · never put in URLs

  • Format: ^[A-Za-z0-9._~+/=-]{8,512}$
beneficiaryIdRequiredstring

JSON body

  • Format: ^[A-Za-z0-9_-]{1,64}$
amountRequireddecimal

JSON body

  • Range: 1 … ∞
  • Decimal places: 2
notesOptionalstring

JSON body

  • Length: 0 … 64
POST
/sendMoney/confirm

Confirm the bank transfer with the OTP

Sandbox only

/api/sandbox/slice/sendMoney/confirm

Sandbox simulation only. No real money moves; live transfers are not enabled for this integration.

POST sendMoney/confirm · Parameter
ParameterTypeRules & handling
tokenRequiredstring

Send in X-OBG-Token

Session token from the login step. Prefer the X-OBG-Token header so it stays out of URLs.

Sensitive · never put in URLs

  • Format: ^[A-Za-z0-9._~+/=-]{8,512}$
otpRequiredstring

JSON body

Sensitive · never put in URLs

  • Format: ^\d{4,8}$

Endpoint identifiers and provider-specific descriptions are kept in English to match the API contract.

Try in sandbox

A request you can inspect.

The console starts in sandbox mode. Use only the public test values there. Switching to Live changes the destination and may use real accounts and funds.

Sandbox

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.

1,000 welcome credits · no card

Small start. Clear cost.

$10 buys 10,000 credits. A successful live request uses one credit; failures and sandbox calls use none. Buying credits does not unlock sandbox-only integrations.

Buy 10,000 credits

Integration guide

Bring it into your code.

Sandbox examples use public fixture values. Live examples use placeholders: keep credentials on your server and never commit them.

Sandbox

curl · POST
curl -X POST 'https://www.openbankinggateway.com/api/sandbox/slice/login/start' \
  -H 'Content-Type: application/json' \
  --data '{
  "phone": "9000000000",
  "pin": "0000"
}'

Sandbox only

Live access not enabled

Contact us to enable access

Live calls for slice Business are enabled per customer. Sandbox mode stays free and needs no sign-in.

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.

Keep exploring.