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

Alma Redirect Component

Add Alma to an existing Components integration.

If you are using Android Components v5.0.0 or later:

This payment method requires no additional configuration.

Follow the Android Components integration guide and use the following module and Component names:

You do not need to collect any information from your shopper in your payments form. If you have an existing Android Components integration, you can use our Redirect Component to redirect the shopper to their bank's website or app where they can complete the payment.

When making a alma payment, you need to:

Before you begin

This page explains how to add Alma to your existing Android Components integration. The Android Components integration works the same way for all payment methods. If you haven't done this integration yet, refer to our Components integration guide.

Before starting your alma integration:

  1. Make sure that you have set up your back end implementation for making API requests.
  2. Add Alma in your test Customer Area.

Show Alma in your payment form

Include alma in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.

  1. Specify in your /paymentMethods request:

The response contains paymentMethod.type: alma.

We provide logos for alma and the issuing banks which you can use on your payment form. For more information, refer to Downloading logos.

Make a payment

When the shopper proceeds to pay, you need to:

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

    • paymentMethod.type: Set this to alma.
    • 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 the RedirectComponent.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.

  1. Pass the action object to your client app. You need this to initialize the Redirect Component.

Handle the redirect

  1. Use the Redirect Component to redirect the shopper to Alma's website where they can provide their account details. When the shopper returns back to your app, the Redirect Component provides the actionComponentData object.

  2. After the shopper returns to your app, make a POST /payments/details request from your server, providing:

    • details: The actionComponentData.details object from the Redirect Component.

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.

See also