DANA Drop-in integration

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:

• Built a Drop-in integration.
• Added DANA in your test Customer Area.

If you want to accept recurring payments, contact your Account Manager to complete the onboarding process.

Recurring payments

Complete the following to make recurring payments for Vipps:

1. Contact our Support Team and ask them to configure vippsAgreementUrl for your account.
   vippsAgreementUrl is a URL that you provide, where the shopper can manage their recurring agreement.
2. Create a shopper token when the shopper is making a Vipps payment.
3. Use the token to make future payments for the shopper.

Create a token

To create a token, include in your /payments request:

• storePaymentMethod: true
• shopperReference: Your unique identifier for the shopper.

When the payment has been authorised, you receive a webhook containing:

• eventCode: RECURRING_CONTRACT
• originalReference: The pspReference of the initial payment.
• pspReference: The token that you need to make recurring payments for this shopper.

Make a payment with a token

To make a payment with saved payment details, include in your /payments request:

• paymentMethod.type: vipps.
• paymentMethod.storedPaymentMethodId: The pspReference from the RECURRING_CONTRACT webhook.
• shopperReference: The unique shopper identifier that you specified when creating the token.
• shopperInteraction: ContAuth.

• recurringProcessingModel: Subscription for subscription payments, or CardOnFile for one-off payments.
  For more information about these parameters, refer to our Tokenization guide.

API reference

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.

Drop-in configuration

There are no configuration steps specific to DANA required for Drop-in.

Recurring

DANA supports recurring transactions. To make recurring transactions, you need to:

1. Create a shopper token.
2. Use the token to make future payments for the shopper.

Create a token

To create a token, include in your /payments request:

• storePaymentMethod: true
• shopperReference: Your unique identifier for the shopper.

When the payment has been settled, you receive a webhook containing:

• eventCode: RECURRING_CONTRACT
• originalReference: The pspReference of the initial payment.
• pspReference: This is the token that you need to make recurring payments for this shopper.

Make a payment with a token

To make a payment with the token, include in your /payments request:

• paymentMethod.storedPaymentMethodId: The pspReference from the RECURRING_CONTRACT webhook.

  You can also get this value using the /listRecurringDetails endpoint.

• shopperReference: The unique shopper identifier that you specified when creating the token.

• shopperInteraction: ContAuth

• 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.