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 Alma in your payment form, and redirects the shopper to complete the payment.
Requirements
Requirement | Description |
---|---|
Integration type | Make sure that you have an existing Advanced flow Android Drop-in integration. |
Setup steps | Before you begin, add Alma in your Customer Area. |
Show Alma 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 alma in your payment form, specify in your /paymentMethods request:
- countryCode: FR
- amount.currency: EUR
After the shopper enters their payment details, Drop-in returns the paymentComponentData.paymentMethod
. Pass this to your server and make a payment request.
Make a payment
When the shopper proceeds to pay, Drop-in returns the paymentComponentData.paymentMethod
.
-
Pass the
paymentComponentData.paymentMethod
to your server. -
From your server, make a /payments request, specifying:
paymentMethod
: ThepaymentComponentData.paymentMethod
from your client app.returnURL
: URL to where the shopper should be redirected back to after they complete the payment. This URL can have a maximum of 1024 characters. Get this URL from the Component in theRedirectComponent.getReturnUrl(context)
.
You can also include the following fields, so that the shopper doesn't have to fill in this information on the Alma-hosted page:
Parameter name | Required | Description |
---|---|---|
telephoneNumber | The shopper's telephone number. | |
shopperEmail | The shopper's email address. | |
billingAddress | The postal address of the shopper. | |
deliveryAddress | The postal address where goods should be delivered. | |
additionalData.alma.installments_count | Set to 3 or 4 to determine the number of installments the shopper will pay. Do not include if you want to let the shopper choose. |
In the /payments response, note the action
object. This contains the information needed to redirect the shopper.
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
: TheactionComponentData.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.
You will also receive the outcome of the payment asynchronously in a webhook.
The resultCode
values you can receive for Alma are:
resultCode | Description | Action to take |
---|---|---|
Authorised | The shopper completed their payment, and it has been sent to the bank for processing. In most cases, this means that you will receive the funds. If you are using manual capture, you also need to capture the payment. | Inform the shopper that the payment has been successful. |
Cancelled | The shopper cancelled the payment while on their bank's website. | 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. The response contains a refusalReason , indicating the cause of the error. |
Pending or Received |
The shopper has completed the payment but the final result is not yet known. | Inform the shopper that you have received their order, and are waiting for the payment to be completed. You will receive the final result of the payment in an AUTHORISATION webhook. |
Refused | The payment was refused by the shopper's bank. | 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 webhooks to know the outcome of the payment. The webhooks you can receive for Alma are:
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
Check the status of Alma test payments in your Customer Area > Transactions > Payments.
Before you can accept live Alma payments, you need to submit a request for Alma in your live Customer Area.