Every rail your customers need, under one roof.
Ten production-grade payment services, sixteen vendor integrations, one API surface. Turn services on per business, per subscription — no code changes required.
Domestic Money Transfer
Cash-to-account transfers to any Indian bank.
Aadhaar Enabled Payments
Cash withdrawal against Aadhaar biometric at the counter.
UPI Payouts
Push money to any VPA or bank account via UPI rails.
Bank Payouts
Bulk NEFT / IMPS / RTGS disbursement at scale.
Credit-Card Bill Pay
Pay any Indian credit card bill from the retailer counter.
Payment Gateway (Wallet top-up)
Let end-users load their wallet from any card / UPI / netbanking source.
Micro-ATM
Card + PIN cash withdrawal from a retailer's terminal.
Express Transfer
Bulk vendor payouts with penny-drop verification.
BrainBucks
In-house rewards + loyalty ledger for your customers.
eVyapar Storefront
Give retailers a mini-storefront + digital catalog + collections.
Money movement
Domestic Money Transfer
Cash-to-account transfers to any Indian bank.
Retailer collects cash from a walk-in customer and sends it to a beneficiary bank account via IMPS or NEFT. The Spoke owns the sender/beneficiary graph; the Hub owns the vendor call. One transaction, one debit, one signed webhook.
Vendors
Who it's for
- Retail counters serving unbanked customers
- Payment aggregators reselling to kirana stores
- SMB payroll disbursement
Flow
- 1Retailer registers sender (KYC + Aadhaar OTP)
- 2Sender adds beneficiary (bank + IFSC + penny-drop verification)
- 3Spoke debits retailer wallet inside DB transaction + writes Outbox row
- 4Hub calls Fino, returns vendor reference
- 5Vendor callback → signed by Hub → verified by Spoke → settled
Limits & policy
- Per transaction
- ₹5,000 – ₹25,000
- Per sender / month
- ₹25,000 (RBI cap)
- Mode
- IMPS · NEFT
- Settlement
- Real-time · webhook confirmed
Highlights
- Idempotent transfers — Idempotency-Key required
- Penny-drop beneficiary verification
- Auto-refund on vendor failure (nightly reconciliation)
- Transaction receipt PDF + SMS out of the box
UPI Payouts
Push money to any VPA or bank account via UPI rails.
Send money instantly to a VPA (e.g. name@upi) or a bank+IFSC pair. Beneficiary is pre-registered at the vendor (race-safe cache in Hub DB) and reused across future payouts to the same VPA.
Vendors
Who it's for
- Marketplace / gig-worker disbursement
- Loan / insurance payout providers
- Refund automation
Flow
- 1Client submits VPA + amount + reference
- 2Hub checks UpiBeneficiary cache, registers on-vendor if new
- 3FrenzoPay: canonical HMAC-SHA512 signing; Decentro: header-only auth
- 4Status polling on `payout/{id}` — 404 handled as NotFound (not error)
- 5Callback + poll converge on identical settlement path
Limits & policy
- Per transaction
- ₹1 – ₹1,00,000
- Beneficiary type
- VPA · Account + IFSC
- Latency
- ~2s to vendor · 5-30s to bank
- Reconciliation
- Polled + webhook · dual-source
Highlights
- Beneficiary auto-cache — pay the same VPA twice, register once
- Idempotency at both Spoke and vendor layer
- Amount handled as int paise end-to-end (no float ever)
- Vendor duplicate-beneficiary reuse (23505 catch + re-read)
Bank Payouts
Bulk NEFT / IMPS / RTGS disbursement at scale.
Programmatic bank transfers with fund-account caching per-beneficiary, X-Payout-Idempotency deduplication, and amount-in-paise conversion. Runs on multiple vendors so payout continuity survives a single-vendor outage.
Vendors
Who it's for
- Payroll processors
- Insurance / claim disbursement
- Vendor & supplier bulk payments
Flow
- 1Client uploads CSV or hits API per-record
- 2Hub creates/reuses PayoutBeneficiary cache (RazorPay fund-account)
- 3One outbound call per record with X-Payout-Idempotency
- 4Vendor async webhook or 5-min status-poll — same settlement service
- 5Failed records auto-refunded, retryable from admin
Limits & policy
- Per transaction
- ₹1 – ₹5,00,000 (mode-dependent)
- Modes
- NEFT · IMPS · RTGS · UPI
- Batch size
- 10,000 records / upload
- Settlement
- Sub-second (IMPS) to ~2h (NEFT)
Highlights
- Fund-account caching (no duplicate registration cost)
- Bulk upload with per-row dry-run validation
- Failure classification: retryable vs. terminal
- Signed downloadable settlement report per batch
Payment Gateway (Wallet top-up)
Let end-users load their wallet from any card / UPI / netbanking source.
PG isn't just a checkout — it's how retailers add float to their Dogma Nexus wallet. Client-ID prefixed on order ID so unauthenticated PG callbacks route back to the right Spoke without a DB lookup. SHA-512 request hash + reverse-hash callback verification (v2 addition — legacy trusted callbacks).
Vendors
Who it's for
- Retailer wallet self-service top-up
- Consumer-facing wallet apps
- Merchant-facing collection tools
Flow
- 1Spoke `POST /api/payment/orders` — creates idempotent WalletFundOrder
- 2Hub `POST /api/payment/prepare` returns hash + form fields
- 3User completes checkout on vendor page
- 4Vendor callback → Hub verifies reverse-hash → routes to Spoke
- 5Deterministic key `pg-topup:{orderId}` — credit exactly once
Limits & policy
- Per transaction
- ₹1 – ₹1,00,000 (KYC-tiered)
- Methods
- Cards · UPI · Netbanking · Wallets
- MDR
- Vendor-defined (transparent to end-user)
- Settlement
- T+1 to retailer wallet
Highlights
- Reverse-hash callback verification (spoof-proof)
- Auto-submit HTML trampoline for SPAs (`/checkout` route)
- Form-field cache for retry (`LastFormFieldsJson`)
- PgTopupReconciliation runs every 5 min for orders > 15 min old
Express Transfer
Bulk vendor payouts with penny-drop verification.
A hybrid of DMT and Payouts: Fino runs penny-drop IMPS/NEFT verification, WaayuPay v2 runs the actual transfer. One keyed router picks the right vendor for each leg based on config.
Vendors
Who it's for
- Corporates paying frequent vendor invoices
- Marketplaces with recurring seller settlement
Flow
- 1Client submits account + IFSC + amount
- 2Fino penny-drop verification (₹1 IMPS + reverse-lookup)
- 3On name-match confidence ≥ threshold → WaayuPay outbound transfer
- 4Auth-in-body clientId+secretKey to WaayuPay `payout/payout`
- 5transferMode discriminates Express from Payout on same endpoint
Limits & policy
- Per transaction
- ₹100 – ₹5,00,000
- Verification fee
- ₹1 penny-drop (refunded)
- Name-match
- Fuzzy score with configurable threshold
- Latency
- ~15s incl. verification
Highlights
- Two-vendor split — verify with A, transfer with B
- Name-match confidence score in every response
- Reject-list of high-risk account patterns
- Same settlement path as Payouts (deterministic key)
Cash-in / cash-out
Aadhaar Enabled Payments
Cash withdrawal against Aadhaar biometric at the counter.
The retailer scans the customer's Aadhaar + biometric fingerprint; Dogma Nexus routes the request to NPCI via the chosen switching partner and, on success, dispenses cash from the retailer's own float. Full 7-method port including Check2FA, Authentication, InitTransaction, MiniStatement, and status polling.
Vendors
Who it's for
- Rural / semi-urban retail micro-ATM operators
- Business correspondents
- BC network aggregators
Flow
- 1Retailer scans customer Aadhaar (12 digits) + captures biometric
- 2Spoke encrypts aadhaar (AES-256-ECB for CredoPay, AES-256-CBC for InstantPay)
- 3Hub routes to primary vendor; falls back to secondary on transport error
- 4Vendor returns SUCCESS/PENDING → wallet credited with deterministic key `aeps-credit:{txnId}`
- 54h–24h reconciler polls Hub `/api/aeps/status` for stuck txns — silent-fail policy retired
Limits & policy
- Per transaction
- ₹100 – ₹10,000
- Per customer / day
- ₹10,000 (RBI cap)
- Operations
- Withdrawal · Balance · Mini-statement
- Settlement
- T+1 via NPCI
Highlights
- MD5-hex `hashed_aadhar` derivation done in-Hub — never in client code
- Two-layer encryption (aadhaar inline + envelope-encrypted body)
- Only WITHDRAWAL credits wallet; enquiries record-only
- CheckStatusAsync poll on 30-min cadence for the recon window
Micro-ATM
Card + PIN cash withdrawal from a retailer's terminal.
The terminal SDK initiates on the retailer's Android device; Dogma Nexus only runs status-check + settlement. Old default-fail policy retired — silently marking stuck txns FAILED would swallow real cash-dispensed events.
Vendors
Who it's for
- Retailers with MATM hardware (MOSAMBEE, Bijlipay, etc.)
- BC network operators with terminal fleet
Flow
- 1Terminal SDK captures card + PIN, initiates txn directly to switch
- 2SDK posts txn ref back to Spoke `POST /api/matm/status`
- 3Hub `POST /api/matm/status` polls CredoPay for ground truth
- 4SettlementService credits with `matm-credit:{txnId}` — exactly once
- 5Reconciler poll every 30 min in the 4h-24h window
Limits & policy
- Per transaction
- ₹100 – ₹10,000
- Operations
- Withdrawal · Balance
- Networks
- Visa · MasterCard · RuPay
- Cash-dispense verified
- Vendor ground truth only
Highlights
- Never default-fails a stuck txn (safety over speed)
- Shared IMatmSettlementService (webhook + reconciler)
- Terminal SDK independence — swap vendors without app change
- Status polling as first-class settlement path
Card & bills
Credit-Card Bill Pay
Pay any Indian credit card bill from the retailer counter.
Customer walks in with a card statement or number; retailer collects cash and pays the bill via a two-step OTP flow. HS256 JWT auth to PaySprint, guaranteed OTP delivery, receipt to customer's phone.
Vendors
Who it's for
- Retail counters offering value-added services
- Fintech apps embedded in QR-code merchant POS
Flow
- 1Retailer enters card number + amount + customer mobile
- 2Hub calls PaySprint `initiate-bill-pay`; OTP sent to customer
- 3Customer reads OTP to retailer; retailer submits step 2
- 4Wallet debit + Hub call inside single DB transaction
- 5Success SMS + PDF receipt to customer's phone
Limits & policy
- Per transaction
- ₹100 – ₹49,999
- Per customer / month
- ₹1,00,000
- Networks
- Visa · MasterCard · RuPay · Amex
- OTP validity
- 5 minutes
Highlights
- HS256 JWT auth — refreshed automatically
- OTP re-send with rate-limit at the Hub
- Auto-refund on 4xx-after-OTP
- Idempotent from step 1 — safe to retry
In-house
BrainBucks
In-house rewards + loyalty ledger for your customers.
A parallel wallet — earn on qualifying transactions (DMT, AEPS, UPI …), burn on discounted services or cash-out. Runs on the same double-entry ledger primitives as the money wallet, so accountants aren't juggling two systems.
Who it's for
- Retention programs for retailer networks
- Cashback on select payment services
- Referral incentives
Flow
- 1Earn rules: config-driven (e.g. `dmt.success → 0.05% credit`)
- 2Ledger insert-only, same schema shape as WalletTransaction
- 3Burn: at checkout, quote available bucks + effective price
- 4Bucks-to-cash rate configurable per business
- 5Full audit + expiration policy
Limits & policy
- Earn rules
- Per-service, config-driven
- Burn rate
- Per-business configurable
- Expiration
- Optional (default: never)
- Ledger
- Double-entry, insert-only
Highlights
- No third-party integration cost
- Runs on identical primitives to money wallet
- Bulk credit / debit for campaigns
- Historical statement per customer
eVyapar Storefront
Give retailers a mini-storefront + digital catalog + collections.
Retailers publish an inventory (products, prices, images), share a link with customers, and collect via UPI or PG. Order + collection + settlement all threaded to the same wallet.
Who it's for
- Kirana stores going digital-first
- Distributors managing downstream retailer catalogs
- Local B2B marketplaces
Flow
- 1Retailer creates catalog in admin (bulk CSV or per-item)
- 2Storefront auto-published at `<biz>.dogmanexus.shop/<retailer>`
- 3Customer scans QR / opens link, selects, checks out
- 4Payment routes via PG or direct UPI collect
- 5Order confirmation + settlement threaded to retailer wallet
Limits & policy
- Catalog size
- Unlimited
- Image hosting
- Included, CDN-delivered
- Checkout methods
- UPI collect · PG (all methods)
- Order status
- Realtime webhook to retailer app
Highlights
- Zero-code storefront per retailer
- Bulk catalog upload + editing
- Inventory sync via API
- Refund flow bound to original wallet credit
Ready to launch a fintech of your own?
We onboard new businesses in about a week. You'll walk out with a live Spoke, your own database, your own Firebase project, and a customer portal at your domain.