Netbanking 2.0

Overview

This guide provides a comprehensive overview of Decentro's Netbanking collection suite.

Decentro's Netbanking capability allows platforms to collect funds securely and seamlessly by letting payers use their preferred banking applications. This feature is part of Decentro's broader Collections suite and supports three distinct modes of checkout, ensuring a flexible payment experience tailored to your application's platform.

Netbanking Flows

Journey

The netbanking process follows a standardized lifecycle across all three modes:

1. Client calls Decentro's Netbanking API
2. Decentro responds with a short link url
3. Payer authorizes payment
4. Decentro responds with webhook/callback

Link/QR Generation: The platform initiates a request to Decentro to generate either a QR Code, an Intent Link, or a Redirection Link. This request must include the consumer_urn (provided by Decentro), the payment amount, the device_type, and other parameters.

Amount Breakup (Optional): Across all three modes, the platform can choose to add amount breakup descriptions. The name field describes the breakup charge, while the value field represents the specific breakup amount. The sum of all breakups must equal the total transaction amount.

Decentro Response: Decentro validates the request and returns a response containing a decentro_txn_id and a short_link_url. The status of the transaction is initially marked as PENDING.

Payer Action:

• QR: The platform displays the QR code. The payer scans it using a preferred bank app.
• Intent: The platform opens the intent link. On Android, it opens an app drawer of available bank apps. On iOS (requires bank_code), it redirects to the specific bank app.
• Redirection: The platform opens the redirection link, redirecting the user to the bank's netbanking login page.

Customer Authorization: The payer logs into their bank app or netbanking portal and authorizes the transaction.

Callback / Status Check:

• Webhook: Decentro triggers a Terminal Transaction Status Callback/Webhook to your pre-configured endpoint with the final status of the transaction once authorized.
• Polling: Alternatively, your platform can proactively check the status using the Get Transaction Status API by passing the decentro_txn_id.

🚧

Beta Feature

Please ensure you only use Staging credentials while testing in the sandbox environment. These APIs are currently in Beta.