Skip to main content
The b2b node contains the settings for shops with business customers. These include access restrictions, customer invitations, the management of employee accounts and the verification of new accounts. The following sections first describe the basic structure and then each sub-node individually.

b2b* - Basic structure

The basic structure of the b2b node is shown below:

Parameter overview


b2b.access - Access restrictions

This lets you configure the access restrictions for B2B customers, for example so that manual activation by the merchant is required before registration is complete.

Example configuration b2b.access

Parameter overview


b2b.userInvitation - User invitation

This is where you configure the email used to invite a customer. The invitation is sent either via the Admin Interface or via the POST customerAccounts/{accountId}/activate endpoint of the Admin Interface API. The email contains a link the customer uses to accept the invitation with the AcceptInvitation action. In the template, you generate this link with the token name AcceptInvitation. Optionally, a reminder email can be sent as long as the invitation has not yet been accepted. The invitation link is valid for the duration defined in invitationLinkValidityInHours, but at least four hours. The same duration applies to the link in the password reset email (token name passwordReset). After the validity period expires, the invitation must be sent again. If reminderActive: true is set, a reminder email is sent for invitations that are still open as soon as reminderIntervalInHours hours have passed since the invitation was sent. Each open invitation receives at most one reminder.
The reminder email does not contain an opt-in token. In the reminder template, $wsOptIn.createTokenUrl() therefore only returns the URL without a token. In the reminder, link for example to a page where the customer can request a new invitation or contact the shop operator.
Example configuration b2b.userInvitation
Parameter overview

b2b.subAccounts - Employee accounts

Configures the invitation email a new employee receives when the administrator of a company account creates their employee account with the SubAccountCreate action. The email contains a link the employee uses to set their password with the ResetPassword action. In the template, you generate this link with the token name ResetPassword (with a capital R). The link is valid for four hours. The redirectTargetForForbiddenViews option also determines where an employee account is redirected when it calls a page that is blocked for its permission group. Example configuration b2b.subAccounts
Parameter overview

b2b.accountVerification - Account verification

Configures the verification process for B2B accounts. The requireEmailVerification and requireManualVerification options control which kind of verification is required. The verificationMerchantEmail option defines the emails sent during activation or on revocation of an account. If requireManualVerification is active, the shop sends this email to the address stored in toAddress as soon as a new account needs to be activated. If requireEmailVerification is also active, the email is only sent after the email address has been confirmed. With permissionsBeforeVerification you define the permissions a not-yet-verified account has in the shop. Example configuration b2b.accountVerification
Parameter overview