ResynPay UI Console

Security model: Client ID & secret stay in your browser (session only). Each action sends them over HTTPS to a short-lived proxy that signs HMAC and forwards to ResynPay — nothing is written to disk or .env. Clear credentials when done. Prefer staging keys for demos; IP-allowlist your network on the credential.

API credentials

not bound

API base URL

Client ID

Client secret

Callback URL for ResynPay member settings: https://uiconsole.magnipay.in/callbacks/resynpay

Payout

Payout provider

Bind credentials, then load providers. A provider can be selected only when payout is enabled for this client and the scheme has a rate for that provider.

Amount (paise)

Beneficiary name

Account number

IFSC

Payment method

Sender mobile

Sender name

Aadhaar

PAN

Beneficiary mobile

State

Bank name

Latitude

Longitude

Txn id (for status)

Charge is quoted by your scheme — do not send charge fields. Amount stays integer paise. Beneficiary mobile, state, and lat/long are optional; leave them blank and the same create body still works. Load providers lists payout providers for the bound client. Only an assigned provider with a scheme rate can be selected. Leave the dropdown on account routing and the create body stays unchanged. Load states calls GET /api/v1/payout/states. Verify account does not debit. Failed payouts return HTTP 400 with status: failed. Bank UTR comes back as utr when the provider returns one.

Inbound callbacks

Recent POSTs to this console’s callback path. Signature verification needs your secret; on an open console we store payloads without verifying.

Response idle

Bind credentials, then run Payout.