Accounts

An account is where payment processing is configured and where a merchant's balance sits. Every account is owned by a company (the legal entity) and linked to it through legal_entity_id (e.g. co_8f3a2b1c). A company can own one or multiple accounts.

Each account configures how payments are accepted, including which payment methods are enabled, in line with the merchant's business profile (industry, sales channels, and so on). Funds from processed payments settle into the account's balance, and payouts to external bank accounts run from it.

Account creation

Accounts are provisioned for a company during onboarding. This version of the Config API exposes account retrieval and configuration, not creation, so a public POST /v1/accounts is not exposed yet. You read an existing account and adjust its configuration through the endpoints below.

The Config API base URL is https://config-api.rootline.com (use https://config-api.staging.rootline.com for staging).

Account readiness

An account can process payments once the owning company is sufficiently verified. This is derived from the company: check that the owning company's verification_status is verified and that its next_action does not require further input from the merchant. See Onboard a company for the full lifecycle.

Coming soon: company capabilities

In addition to the verification_status and next_action, company capabilities will soon be available. Capabilities are high-level (payments and payouts) and indicate per capability whether the merchant is allowed to use it, giving you a precise signal for what an account can do.

The account object

{
  "id": "acc_3VfPsTP2kqnjR6LHnOdpVe",
  "object": "account",
  "display_name": "Coffee Corner Amsterdam",
  "description": "In-store and online payments for the Amsterdam location",

  "legal_entity_id": "co_8f3a2b1c",
  "business_address": {
    "street_address": "Prinsengracht 449",
    "postal_code": "1016HN",
    "city": "Amsterdam",
    "country": "NL"
  },

  "display_options_id": "disp_4hCDUAURjeIKPOxlM1cC7C",
  "publishable_keys": ["apk_1aFvRxiyzgLjPXJAhOtVsY"],
  "allowed_domains": ["coffeecorner.nl", "shop.coffeecorner.nl"],

  "payment_method_settings": [
    { "payment_method": "ideal" },
    {
      "payment_method": "applepay",
      "applepay_settings": {
        "merchant_url": "https://shop.coffeecorner.nl",
        "domains": ["shop.coffeecorner.nl"]
      }
    }
  ],

  "created_at": "2026-06-24T10:35:00Z"
}

Field	Type	Description
`id`	string	Unique identifier for the account, prefixed `acc_`.
`object`	string	Always `account`.
`display_name`	string	Human-friendly name of the account.
`description`	string	A description of the account.
`legal_entity_id`	string	The `company` (legal entity) that owns the account. See Onboard a company.
`business_address`	object	The account's business address. Fields: `street_address`, `street_address2`, `postal_code`, `city`, `state`, `country`.
`publishable_keys`	string[]	Publishable key(s) used to initialize the SDK.
`allowed_domains`	string[]	Payment flows for this account are restricted to these domains.
`payment_method_settings`	object[]	Per payment method configuration. See Payment method settings below.
`created_at`	string	When the account was created.

Retrieve an account

GET /v1/accounts/acc_3VfPsTP2kqnjR6LHnOdpVe
x-api-key: <your-api-key>
rootline-version: 2024-04-23

Returns the full account object, including its allowed domains and payment method settings inline.

Allowed domains

Payment flows for an account are restricted to the domains on its allowed list. A checkout served from a domain that is not on the list is rejected, which protects the account's keys from being used elsewhere.

See Allowed domains for how to list, add, and remove domains via the API.

Payment method settings

Each entry in payment_method_settings configures one payment method (for example ideal or applepay) for the account. Some methods carry no extra configuration; others, such as Apple Pay, require method-specific settings.

List payment method settings

GET /v1/accounts/{account_id}/payment-method-settings

Get a single payment method setting

GET /v1/accounts/{account_id}/payment-method-settings/{payment_method}

Update a payment method setting

PATCH /v1/accounts/{account_id}/payment-method-settings/{payment_method}
x-api-key: <your-api-key>
rootline-version: 2024-04-23
Content-Type: application/json

{
  "applepay_settings": {
    "merchant_url": "https://shop.coffeecorner.nl",
    "domains": ["shop.coffeecorner.nl"]
  }
}

applepay_settings carries the merchant_url and the list of registered domains for Apple Pay. See Enable Apple Pay for the full domain-verification flow.

Get a payment method's domains

GET /v1/accounts/{account_id}/payment-method-settings/{payment_method}/domains

Returns the domains registered for that specific payment method.

Publishable keys

publishable_keys are the public keys your client-side integration uses to initialize the SDK for an account. They are safe to expose in front-end code. They identify the account a payment flow belongs to, and they only work from the account's allowed domains.

See Retrieving the accountPublishableKey for how to fetch a publishable key for an account.

Account creation​

Account readiness​

The account object​

Retrieve an account​

Allowed domains​

Payment method settings​

List payment method settings​

Get a single payment method setting​

Update a payment method setting​

Get a payment method's domains​

Publishable keys​