Merchant Account Status - Native Partners

1. PENDING The initial state until the merchant submits the widget.
2. ADDITIONAL_REVIEW_1 (optional) When the merchant underwriting can't approve transactions automatically. It must be done manually.
3. TRANSACTIONS_ENABLED The merchant can start to transact
4. ADDITIONAL_REVIEW_2 (optional) When the merchant underwriting can't approve payouts automatically. It must be done manually.
5. PAYOUTS_ENABLED The merchant is fully underwritten and can transact and receive payouts.
6. SUSPENDED (optional) At any point in time the merchant might get suspended by Klarna. Either the merchant underwriting rejected the merchant, illegal activities have been detected and the merchant was manually suspended or the merchant reached out to Klarna and asked for cancellation.

Test Merchant Account Status Changes in Playground

The Merchant Onboarding API - Native Partners does not execute merchant underwriting in the playground environment. Instead, it reacts to two markers in the merchant's email address to automatically move a merchant forward in the onboarding process including the corresponding status callbacks execution.

faketransactionsapproved

When the merchant's email address contains faketransactionsapproved the merchant will be moved forward till TRANSACTIONS_ENABLED state.

fakepayoutsapproved

When the merchant's email address contains fakepayoutsapproved the merchant will be moved forward till PAYOUTS_ENABLED state.

Please note that possibly missing data such as test bank account details might cause a stuck merchant before PAYOUTS_ENABLED is reached.

Example

The following example (filled with additional data) will create and move the merchant forward till TRANSACTIONS_ENABLED state calling the partner's callback URL for the status update.

POST /accountmanagement/v1/merchant

{
  "email": "john.doe+faketransactionsapproved@example.com"
  ...
}