Workspace and environment
Credentials are scoped to a workspace and environment. Sandbox and live records remain separate.
Integration
Bring India-linked settlement into your payment product through a shared workflow for beneficiaries, quotes, authorization, execution status and reconciliation.
Start with a verified Indian beneficiary, the exact INR amount the recipient should receive and the commercial purpose. Funding currency, payment requirements, FX and provider execution belong to the same settlement record.
Define beneficiary, recipient amount, purpose and your own reference. Check the requirements and quote before asking for authorization.
Keep creation and authorization as separate permissions. Follow the recorded state and address a specific requirement when action is needed.
Connect delivery evidence, provider references and the final receipt to your own operating records.
Credentials are scoped to a workspace and environment. Sandbox and live records remain separate.
Use a stable idempotency key for each logical settlement creation or authorization. An uncertain provider outcome needs review before resubmission.
Verify webhook signatures, record event identifiers and tolerate duplicate deliveries. Your system should not infer finality from a single provider response.
Retain settlement references and reconciliation outcomes so your team can trace the result after execution.
Share your business role, jurisdictions, proposed funding currency, Indian destination, use case and indicative volume. We will discuss route eligibility, provider responsibilities, access and acceptance criteria.
The public workspace is a demonstration. API access, supported routes and commercial terms are confirmed during onboarding; this website does not issue production credentials or initiate payments.
Review the provider integration model →