On this page, you can find additional configuration for adding DANA to your Drop-in integration.
Before you begin
This page assumes you have already:
You don't need to send additional fields for DANA. To see optional fields that you can send for all payment methods, choose the endpoint you integrated:
- /sessions: This is the default with Drop-in v5.0.0 or later.
- /payments: If you implemented an additional use case.
There is no required DANA-specific integration for Drop-in.
Recurring paymentsDANA supports recurring transactions. To make recurring transactions, you need to:
Create a token
To create a token, include in your /payments request:
- shopperReference: Your unique identifier for the shopper.
When the payment has been settled, you receive a webhook containing:
pspReferenceof the initial payment.
pspReference: This is the token that you need to make recurring payments for this shopper.
Make sure that your server is able to receive RECURRING_CONTRACT as part of your standard webhooks. You can enable the RECURRING_CONTRACT event code in the webhook settings page.
Make a payment with a token
To make a payment with the token, include in your /payments request:
pspReferencefrom the RECURRING_CONTRACT webhook.
You can also get this value by using the /listRecurringDetails endpoint.
shopperReference: The unique shopper identifier that you specified when creating the token.
recurringProcessingModel: Use Subscription for a series of transactions following a fixed time interval or UnscheduledCardOnFile for contracts with non-fixed time interval.
Test and go live
To test successful DANA live payments, you need to use a real mobile number registered with a DANA account.
If you are encountering issues with testing DANA payments, contact our Support Team.
Check the status of DANA test payments in your Customer Area > Transactions > Payments.
Before you can accept live DANA payments, you need to submit a request for DANA in your live Customer Area.