Onboarding checklist
Everything you need to hand over to Walley in order to get the Loyalty Booster enabled and your loyalty adapter configured.
Overview
The Loyalty Booster is configured per store by Walley. Before it can be activated, Walley needs a set of details about your loyalty program and, if you use a custom loyalty adapter, about the API you host.
Collect the information below and send it to your Walley representative or to help@walley.se. Configuration is done separately per environment, so provide the details for both test and production (share any credentials/secrets via a secure channel, not by email).
Never send credentials or other secrets, such as the Basic authentication password for your adapter, by email or chat. Ask your Walley representative for a secure channel and share them there.
This functionality is at an early stage and is not yet available for all merchants. Please contact your Walley representative for more information.
1. Stores and markets
| Information | Required | Description |
|---|---|---|
| Store id(s) | Yes | The Walley store id(s) the loyalty adapter should be enabled for. One configuration is made per store. |
| Environment | Yes | Whether the configuration applies to test or production. Provide the details for both. |
| Markets and languages | Yes | The countries and languages the loyalty program should be offered in. |
| B2C / B2B | Yes | Which customer types the loyalty program applies to. See the supported markets in the introduction. |
2. Loyalty program details
| Information | Required | Description |
|---|---|---|
| Provider | Yes | Which adapter to use, for example Voyado or a custom adapter. |
| Membership name | Yes | The name of the loyalty program shown to the customer, for example ABC Reward Club. |
| Terms URL | Yes | A publicly available URL with the terms and conditions of the loyalty program, per language. |
| Application text | No | The text shown to the customer in the checkout, per language. See application text for supported formatting. |
| Registration number | Yes | Whether a registration number (for example a social security number) is required to create a membership. |
| Loyalty color | No | The color used in the loyalty module. Set with the data-loyalty-color attribute, and falls back to data-action-color. |
membershipName, termsUri and applicationText are returned by the custom adapter per request and are localized using the locale query parameter. If you use a custom adapter, you only need to confirm which languages you support.
3. Custom adapter connection details
Only needed if you host your own custom loyalty adapter.
| Information | Required | Description |
|---|---|---|
| Base URL | Yes | The HTTPS base URL of your adapter, for example https://your-adapter.com/api/v1. Provide one URL per environment. |
| Basic auth username | Yes | The username Walley uses for Basic Authentication against your adapter. |
| Basic auth password | Yes | The corresponding password. Share it through a secure channel, never by email or chat. |
| API version | Yes | The version of the custom loyalty adapter API your implementation follows. |
| Endpoints exposed | Yes | Confirmation that both GET /membership and POST /membership are implemented as described in the custom adapter documentation. |
Your adapter must be reachable from Walley over HTTPS, respond within 10 seconds, and accept 1 retry after a 2 seconds back-off for server errors. Requests that time out or return a non 2xx response result in the membership not being shown or not being created.
4. Contacts
| Information | Required | Description |
|---|---|---|
| Technical contact | Yes | Name and email of the person responsible for the adapter integration. |
| Business contact | Yes | Name and email of the person responsible for the loyalty program. |
| Support contact | No | Where Walley should report incidents related to the adapter. |
| Planned go-live date | Yes | When you plan to activate the Loyalty Booster in production. |
Checklist
- Store id(s), environment, markets and languages are specified
- Membership name and terms URL are provided for every language
- It is decided whether a registration number is required to create a membership
- The adapter base URL is reachable over HTTPS from Walley, in both test and production
- Basic authentication credentials are shared with Walley through a secure channel
- Both the Get Membership and Create Membership endpoints are implemented and tested
- Your integration handles the
walleyCheckoutCrmUpdatedevent and readsdata.customer.loyaltyMembershipfrom the checkout information - A routine exists to create memberships manually if a registration fails for technical reasons
- Technical and business contacts and a planned go-live date are shared with Walley
Next steps
When Walley has received the information, the adapter is configured for your test store so you can verify the flow end to end. Once the integration is verified, the same configuration is applied to your production store.
For the overall integration, also go through the go-live checklist.