Merchant Onboarding overview
If you operate a platform that signs up its own sub-merchants (a marketplace, an aggregator, an ISO), you can onboard them onto Omniware programmatically with the Register Merchant API.
How it works
- Collect KYC and bank details
Build a form on your dashboard that gathers everything Omniware needs: business name, login, PAN, bank account, address, contact, optional GSTIN and Aadhaar.
- Encrypt the payload
Serialise to JSON and AES-256-ECB encrypt with the encryption key Omniware provided to you. (Note: ECB, not CBC — this is the only endpoint that uses ECB.) See Encryption.
- POST to Register Merchant
The
access_keystays in plaintext alongside the encrypted body so Omniware knows which key to use to decrypt. - Receive the new merchant's credentials
Omniware returns the new merchant's
api_key,salt, and (optionally) a BharatQR static QR image. A verification email is sent to the merchant's address.
What you need from Omniware
| Credential | Purpose |
|---|---|
access_key | Identifies your parent account on the registration request. |
encryption_key | AES-256-ECB key for encrypting the request body. |
referral_code | Your referral code, embedded inside the encrypted payload. |
Contact your Omniware relationship manager to get these provisioned.