Payments apps and their data APIs

Wallets, UPI and payment apps — the endpoints that move money, check balances, and confirm transfers behind the scenes.

Payment apps hide some of the most structured data in mobile: balances, ledger entries and transfer confirmations behind wallet, checkout and till screens. Paytm reads wallet balance (accountBalance.value, sub-wallet breakdown) and pages the passbook at POST /v1/wallet/statement with per-transaction txnStatus, amount and counterparty. Square Point of Sale carries the merchant side — checkout charges with amount_money, tip_money and receipt_url — while inyad Konnash syncs credit-book entries, cash drawers and wallet transfers for small shops.

Frequently asked questions

Which payment apps here expose a wallet balance API?

Paytm does: POST /v1/wallet/balance returns accountBalance.value, per-sub-wallet details and min/max transaction limits. inyad Konnash returns walletAccounts with balanceInCents in its session bootstrap, and Square exposes merchant balance and deposit data behind the signed-in merchant session.

Do these apps share a common auth pattern?

All three are token-based but differ in detail. Paytm sends an SSO session cookie plus user and channel token headers, Square uses a Bearer merchant session, and inyad Konnash bootstraps a session that issues accessToken and refreshToken pairs.

Can I get transaction history, not just balances?

Yes. Paytm's POST /v1/wallet/statement pages the wallet passbook with txnId, txnStatus, txnamount, narration and counterparty fields. inyad Konnash syncs credit-book and cashbook transactions per customer, and Square returns payment, order and loyalty records for the merchant.