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

Walley for API-only

Add Walley to an existing API-only integration.

Accept Walley payments using our APIs, and build your own payment form to have full control over the look and feel of your checkout page.

Before you begin

Before continuing, complete the following:

Build your API-only integration.
Add Walley in your Customer Area by contacting our Support Team.

Walley requires at least Checkout API v66.

Build your payment form for Walley

Include Walley in the list of available payment methods.

To make a Walley payment, collect the following shopper details:

If you are using the /paymentMethods endpoint to show available payment methods to the shopper, specify these parameters:

Parameter	Possible values
countryCode	- DK - FI - NO - SE
amount.currency	- DKK - EUR - NOK - SEK

Payments in Denmark (DK) or with the DKK currency are available only for B2C payments.

The API response contains paymentMethod.type: walley.

Adyen provides a logo for Walley that you can use on your payment form. For more information, refer to Downloading logos.

Make a payment

You must include the following fields when making a /payments request:

Parameter name	Required	Description
telephoneNumber		The shopper's telephone number. You must collect a working mobile phone number (including country code) from the customer. Incorrect or missing numbers will fail Walley's validation.
shopperEmail		The shopper's email address.
lineItems.id		The ID of the line item.
lineItems.description		A description of the line item.
lineItems.amountExcludingTax		The item amount excluding the tax, in minor units.
lineItems.taxAmount		The tax amount, in minor units.
lineItems.taxPercentage		The tax percentage, in minor units.
lineItems.quantity		The number of items.

In the /payments response, note the action object. This contains the information needed to redirect the shopper.

Handle the redirect

To complete the payment, redirect the shopper to the action.url returned in the /payments response.

When using the HTTP GET method:
For security reasons, when displaying the redirect in the app, we recommend that you use SFSafariViewController for iOS or Chrome Custom Tabs for Android, instead of WebView objects. Also refer to the security best practices for WebView.
After the shopper is redirected back to your website, check the payment result by making a POST /payments/details request, specifying:
- details: object that contains the URL-decoded redirectResult returned when the shopper was redirected back to your site.
In the response note the following:
- resultCode: use this to present the result to your shopper.
- pspReference: our unique identifier for the transaction.

Show the payment result

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

You can receive the following resultCode values for Walley:

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've 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.

You also receive the outcome of the payment asynchronously in a webhook. If the shopper failed to return to your website or app, wait for notification webhooks to know the outcome of the payment. You can receive the following notification webhooks for Walley:

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

There is no test environment available for Walley. Verify payments with real payment details and small amounts.

Check the status of Walley verification payments in your Customer Area > Transactions > Payments.