My EMI Pay
  1. Application journey
  • My-EMI Lending API
  • System
    • Health check
      GET
  • Products
    • List published loan products
      GET
  • Auth
    • Request OTP
      POST
    • Verify OTP
      POST
    • Refresh tokens
      POST
    • Select a family account after OTP
      POST
    • Add a family member on this phone
      POST
    • Logout
      POST
    • Send email verification link
      POST
    • Email verification status
      GET
    • Confirm email verification (Bearer)
      GET
    • Confirm email verification token (Bearer)
      POST
    • iOS Universal Links association
      GET
    • Android App Links association
      GET
    • List family profiles on this phone
      GET
    • Resend OTP
      POST
  • Profile
    • Get customer profile
    • Update customer profile
  • Applications
    • Get current application screen
    • Begin verification
    • Verify PAN
    • Acknowledge credit score
    • Accept offer
    • Create loan
    • Request payout
  • Application journey
    • Application journey
      GET
    • Start PAN KYC via DigiLocker
      POST
    • PAN KYC status
      GET
    • Start Aadhaar KYC via DigiLocker
      POST
    • Aadhaar KYC status
      GET
    • Edit Aadhaar communication address
      POST
    • Verify bank account (KYC)
      POST
    • Start eSign
      POST
    • eSign status
      GET
    • Bureau report
      GET
    • Loan eligibility
      GET
    • Complete PAN KYC (poll DigiLocker)
      POST
    • Complete Aadhaar KYC (poll DigiLocker)
      POST
    • Pull bureau report
      POST
    • Start mock e-NACH
      POST
    • Mock e-NACH status
      GET
    • HTML origination document pack
      GET
    • Start bank statement consent
      POST
    • Poll bank statement consent
      GET
  • Webhooks
    • Resolve or fail bureau claim
    • Resolve or fail KYC claim
    • Resolve or fail eSign claim
    • Resolve or fail income claim
  • Ops
    • Dispatch due outbox handlers
    • Poll workflow timers
    • Redrive dead-letter handler
  • Other
    • List published originators
    • HTML origination pack for one originator
  1. Application journey

Start bank statement consent

POST
https://api-dev.myemipay.com/application/income/consent
Last modified:2026-09-25 07:30:30
Start bank statement consent
Description: starts an Account Aggregator bank link. The customer approves read-only statement access in their AA app. We never see the bank password.
Usage: when the app wants salary from statements. Optional relative to the main journey — it does not block PAN or Aadhaar.
Details: needs the verified login mobile. Body may set redirectUrl (default myemi://aa/callback). 201 is { status: "requested", url }. Open url. A mock url contains mock-fineye.local and the next status poll is already completed.
Next: GET /application/income/status until status is completed, rejected, revoked, or expired.
Auth: Authorization: Bearer {{accessToken}}
Errors: 401 unauthorized | session_expired · 422 validation_failed — no verified mobile

Request

Authorization
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
Header Params

Body Params application/json

Examples

Responses

🟢201Consent link
application/json
Bodyapplication/json

🟠401Unauthorized
🟠422A verified mobile number is required before connecting a bank
Request Request Example
Shell
JavaScript
Java
Swift
curl --location 'https://api-dev.myemipay.com/application/income/consent' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
  "redirectUrl": "https://trulens.in"
}'
Response Response Example
201 - Consent link
{
  "status": "requested",
  "url": "https://aa.example/consent/handle"
}
Modified at 2026-09-25 07:30:30
Previous
HTML origination document pack
Next
Poll bank statement consent
Built with