This page explains how to add Walley to your existing iOS Drop-in integration.
Requirements
Requirement | Description |
---|---|
Integration type | Make sure that you have built your Drop-in integration. Walley for iOS works with all versions of Drop-in. |
Setup steps | Before you begin, contact our Support Team to add Walley in your test Customer Area. |
API reference
You must include the following fields when making a /sessions 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. | |
company.name | The name of the company making the payment. This will be prefilled and presented to the shopper on Walley's payment form. Only required for walley_b2b payments. | |
company.registrationNumber | Only relevant to business-to-business payments. The registration number of the company making the payment. | |
lineItems.id | The ID of the line item. | |
lineItems.description | A description of the line item. Maximum length: 50 characters. | |
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. |
Drop-in configuration
There is no required Walley-specific integration for Drop-in.
Test and go live
You can perform the test scenarios described on Walley's technical documentation using Adyen's /payments endpoint. Consider the following:
- Include the
CivRegNo
as the socialSecurityNumber. - When testing a Walley B2B transaction, provide the company information as shown in the following example:
"company": { "name": "Adyen N.V.", "registrationNumber": "5562000116" }
Check the status of Walley verification payments in your Customer Area > Transactions > Payments.