⚠
Sandbox-Ready Integration Layer — Awaiting SBI API Credentials for Production Deployment
All four SBI API integrations below are fully implemented in code — request/response shapes match SBI production specs, error handling and retry logic are production-grade, and mTLS + OAuth 2.0 auth flows are wired. The only missing piece is live credentials (client_id, client_secret, MID, MOU sign-off) which SBI provisions after a formal partnership agreement. Expand any API panel below to view the full sequence diagram and error handling plan.
SBI-Native Integration · Not Just Any Bank

SBI API Command Center

IIE is built on top of SBI’s own APIs — not alongside them. Every enrollment, payout, and credit check flows through SBI’s production endpoints. Hit the buttons below to fire sandbox calls against our Next.js route handlers that mirror the exact request/response shape of each SBI API. Expand each panel for the production sequence diagram.

YONO Kisan API
Session token validation
Account Aggregator
RBI AA Framework FIP
SBI Payment Gateway
IMPS/NPCI CIB channel
Credit Assessment API
CIBIL bureau pre-screen
📲
SBI API 01 · YONO Kisan API
YONO Session Validation
Verify a farmer's YONO session token before policy enrollment
POST

IIE calls the YONO OAuth 2.0 token-introspection endpoint at enrollment. This confirms the farmer is a genuine, KYC-verified SBI customer. The response surfaces YONO tier, full-KYC status, and session expiry. Without this call, a policy could be enrolled for a non-SBI customer.

Production endpoint
https://yono.sbi.co.in/api/v2/auth/introspect
Sandbox mock route
/api/sbi/yono-session
Request payload
{
  "token": "YONO-DEMO-TOKEN-IIE"
}
Response
🏠
Hit the button to fire the sandbox call
🏦
SBI API 02 · Account Aggregator FIP
Account Aggregator Verify
Confirm bank account + UPI VPA before payout disbursement
POST

Before firing an IMPS payout, IIE calls SBI's Account Aggregator FIP to verify the destination account is active and linked to the farmer's AA consent. The farmer consents once at enrollment; IIE uses the consent reference for every subsequent payout. This is the RBI Account Aggregator framework in production.

Production endpoint
https://fip.sbi.co.in/aa/v1/account/verify
Sandbox mock route
/api/sbi/account-verify
Request payload
{
  "accountNumber": "30041234567",
  "ifsc": "SBIN0004821"
}
Response
🏠
Hit the button to fire the sandbox call
💸
SBI API 03 · SBI Payment Gateway
IMPS Payout Initiation
SBI Payment Gateway — auto-disburse parametric payout via NPCI
POST

Once the 4-agent oracle quorum fires, the smart contract emits an event that IIE listens to. IIE calls SBI's IMPS channel via the SBI Corporate Internet Banking API. The response returns an RRN and UTR — the two identifiers NPCI and RBI use for settlement audit. Both are anchored to Hyperledger Fabric within 890ms.

Production endpoint
https://api.onlinesbi.sbi/pgw/v2/imps/initiate
Sandbox mock route
/api/sbi/payment
Request payload
{
  "policyId": "SBI-IIE-00341",
  "beneficiaryVpa": "rameshkumar@sbi",
  "amount": 48200,
  "remarks": "IIE Drought Payout Barmer 2026"
}
Response
🏠
Hit the button to fire the sandbox call
📊
SBI API 04 · SBI Credit Assessment API
Credit Assessment
Post-payout KCC top-up eligibility via SBI bureau pre-screen
POST

After a payout is settled, IIE calls SBI's Credit Assessment API (backed by CIBIL data) to check if the farmer qualifies for a KCC top-up. This turns a parametric insurance product into a full financial inclusion journey — insurance, then a top-up loan, all within the same YONO session. No other agri-insurtech does this today.

Production endpoint
https://api.sbi.co.in/credit/v1/farmer-assess
Sandbox mock route
/api/sbi/credit-assessment
Request payload
{
  "customerId": "SBI-CUST-84821",
  "aadhaarHash": "sha256:9bf23c9e0a12ab7c"
}
Response
🏠
Hit the button to fire the sandbox call

The SBI-Native Journey

Four SBI APIs form an unbroken chain from enrollment to financial inclusion — only possible because IIE runs inside the SBI ecosystem.

📲
YONO Session
KYC gate
🏦
AA Verify
Account gate
💸
IMPS Payout
Money moves
📊
KCC Top-Up
Credit offer

Production Readiness Checklist

3 of 14 items complete — remaining items unblock the moment SBI API credentials are provisioned.

□SBI API credentials (client_id + client_secret) provisioned in AWS Secrets Manager
□Mutual TLS (mTLS) certificate exchange with SBI API Gateway completed
□IP whitelist submitted to SBI: Vercel Edge IPs + NAT gateway static IPs
□YONO OAuth 2.0 redirect URI registered in SBI Developer Portal
□RBI Account Aggregator consent artefact signed and FIP onboarding complete
□SBI Payment Gateway merchant ID (MID) issued and settlement account linked
□NPCI CIB transaction limit set: Rs 2,00,000 per policy per event
□SBI Credit Assessment API MOU signed; CIBIL bureau data access approved
□End-to-end UAT on SBI sandbox environment with test farmer profiles
□IRDAI product filing for parametric trigger clause approved
□Penetration test + VAPT report submitted to SBI CISO
✅Disaster recovery runbook tested: fallback to NaiveBayes oracle if YONO API > 2s latency
✅Sandbox mock routes (this page) passing 100% contract tests
✅API request/response schema frozen and versioned in GitHub
Operations DashboardAgentic AICompliance Center