No momento, esta página não está disponível em português
Payment-method icon

MobilePay Android Drop-in

Add MobilePay to an existing Android Drop-in integration.

If you are using Android Drop-in v5.0.0 or later:

This payment method requires no additional configuration.

Follow the Drop-in integration guide.

Our Android Drop-in renders MobilePay in your payment form, and redirects the shopper to the MobilePay app on their mobile device to complete the payment. As with other redirect payment methods, you need to check the payment result after the shopper returns to your app.

To give your shoppers a better experience, you can also send the shopper's telephone number when making the payment, so they no longer have to provide this later when they are redirected to MobilePay.

Requirements

Requirement Description
Integration type Make sure that you have built an Advanced flow Android Drop-in integration.
Setup steps Before you begin, add MobilePay in your Customer Area.

Show MobilePay 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 MobilePay in your payment form:

  1. Make a POST /paymentMethods request specifying one of the following combinations:

    Country/region countryCode amount.currency amount.value
    Denmark DK DKK The value of the payment, in minor units.
    Finland FI EUR The value of the payment, in minor units.

  2. When the shopper proceeds to pay, Drop-in returns the paymentComponentData.paymentMethod.

    Pass the paymentComponentData.paymentMethod to your server — these are the shopper details that you need to make the payment.

Make a payment

From your server, make a POST /payments request, specifying:

  • paymentMethod: The paymentComponentData.paymentMethod from your client app.
  • telephoneNumber: Optional. If you already have your shopper's phone number, send it in the request so they no longer have to provide this later when they are redirected to MobilePay.
  • returnUrl: URL to where the shopper should be redirected back to after they complete the payment. Get this URL from the Component in the RedirectComponent.getReturnUrl(context).
In the  /payments response, note the `action` object. This contains the information needed to redirect the shopper.

<div data-component-wrapper="code-sample">
<code-sample
    :title="'/payments response'"
    :id="''"
    :code-data="[{&quot;language&quot;:&quot;json&quot;,&quot;tabTitle&quot;:&quot;&quot;,&quot;content&quot;:&quot;{\n   \&quot;resultCode\&quot;:\&quot;RedirectShopper\&quot;,\n   \&quot;action\&quot;:{\n      \&quot;paymentMethodType\&quot;:\&quot;mobilepay\&quot;,\n      \&quot;method\&quot;:\&quot;GET\&quot;,\n      \&quot;url\&quot;:\&quot;https:\/\/checkoutshopper-test.adyen.com\/checkoutshopper\/checkoutPaymentRedirect?redirectData=...\&quot;,\n      \&quot;type\&quot;:\&quot;redirect\&quot;\n   }\n}&quot;}]"
    :enable-copy-link-to-code-block="true"
    :code-sample-card-size="'fullsize'"
></code-sample>

If your integration is set up correctly, the action object is passed from your server to the client.

Check the payment result

Drop-in redirects the shopper to complete the payment. When the shopper returns back to your app, Drop-in provides the actionComponentData object.

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

  • details: The actionComponentData.details object from Drop-in.

You receive a response containing:

  • resultCode: Use this to present the payment result to your shopper.
  • pspReference: Our unique identifier for the transaction.

Present the payment result

Use the  resultCode that you received in the /payments/details response to present the payment result to your shopper.

The resultCode values you can receive for MobilePay are:

resultCode Description Action to take
Authorised The payment was successful. Inform the shopper that the payment has been successful, and proceed with the order.
You receive the funds after the payment has been captured.
Cancelled The shopper cancelled the payment. Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.
Error There was an error when the payment was being processed. Inform the shopper that there was an error processing their payment.
Refused The payment was refused. Ask the shopper to try the payment again using a different payment method.

If the shopper failed to return to your website or app, wait for the AUTHORISATION webhook to receive the outcome of the payment:

eventCode success field Description Action to take
AUTHORISATION false The transaction failed. Cancel the order and inform the shopper that the payment failed.
AUTHORISATION true The shopper successfully completed the payment. Inform the shopper that the payment has been successful, and proceed with the order.

Test and go live

MobilePay cannot be tested on the test environment. Use live penny tests (payments for a minimal amount) instead.

  1. Make sure that you have access to a live MobilePay account that is coupled with a Visa, Mastercard, or Dankort account, and a valid phone number.
  2. Submit a request for MobilePay in your live Customer Area.
  3. After MobilePay is added to your Customer Area, make a payment for a minimal amount choosing MobilePay as the payment method.
  4. Check the status of the penny test in your live Customer Area > Transactions > Payments.

Go live

Before you can accept live MobilePay payments, you need to submit a request for MobilePay in your live Customer Area.

See also