DuitNow Drop-in integration

Our iOS Drop-in renders DuitNow in your payment form, and generates a QR code that the shopper uses to pay with their choice of app from DuitNow participating banks.

Requirements

Select the server-side flow that your integration uses:

Show DuitNow in your payment form

Drop-in uses the countryCode and the amount.currency from your /paymentMethods request to show the available payment methods to your shopper.

To show DuitNow in your payment form, you need to specify in your /paymentMethods request:

• countryCode: MY
• amount.currency: MYR
• amount.value: The value of the payment.

After the shopper selects a payment method and provides payment details, Drop-in invokes the didSubmit method which contains data.paymentMethod. Pass data.paymentMethod to your server and make a payment request.

Make a payment

When the shopper proceeds to pay, Drop-in invokes the didSubmit method which contains data.paymentMethod.

1. Pass data.paymentMethod to your server.

2. From your server, make a /payments request, specifying:

   • paymentMethod: The data.paymentMethod from the didSubmit event from your client app.

   Drop-in generates the QR code that the shopper uses to pay.

Check the payment result

To check the payment result, use the state.data object from the corresponding event handler:

• onAdditionalDetailsfor successful payments.
• onError for unsuccessful or timed out payments.

From your server, make a POST /payments/details request with:

• details: the state.data.details from the onAdditionalDetails or onError event.
• paymentData: the state.data.paymentData from the onAdditionalDetails or onError event.

You receive a response containing:

• additionalData: Object containing the value and currency for the payment.
• pspReference: Our unique identifier for the transaction.
• resultCode: Authorised for successful payments or Refused for unsuccessful or timed-out payments. Use this to present the payment result to your shopper.

Show the payment result

Use the resultCode from the /payments/details response to show the payment outcome on your frontend.

You will also receive the outcome of the payment asynchronously in a webhook.

The resultCode values you can receive for DuitNow are:

If you are implementing an additional use case, you can make a /payments/details call to receive an immediate response.

Test and go live

You can test your integration in two ways: with the Adyen Payment Simulator, or directly with .

Test with Adyen

Use the Adyen Payment Simulator to verify that your integration works correctly with Adyen. You can test during development, before you go live, and after launch. The simulator does not recreate the shopper's journey through the app or website.

This testing option is available by default when you add in your test Customer Area. The payment method type is duitnow.

To test a QR code payment:

1. Start a payment as usual in your integration. Your integration shows a QR code.
2. Scan the QR code as the shopper, then select the payment outcome that you want to test on the Adyen-hosted simulator page.
3. Wait for the webhook message with the final payment outcome. There is no shopper redirect and no /payments/details request. If you use Drop-in, it refreshes automatically with the outcome that you selected.
4. Confirm that your integration handles the outcome, and that the payment appears in your Customer Area > Payments > Payment list.

Test directly with DuitNow

You can also test DuitNow payments directly with real payment details and small amounts.

Check the status of direct DuitNow test payments in your Customer Area > Payments > Payment list.

To accept live DuitNow payments, you must contact our Support Team to add DuitNow in your live Customer Area.

See also