Skip to main content

Account activation

Rootline Accounts are fundamental to enabling you and your merchants to receive payments. Each user can have one or multiple accounts, providing flexibility in payment processing and fund management.

To find the accounts that have been created for you and your users, navigate to the Accounts overview page in the Rootline dashboard. Each account comes with an account_id that can be provided in the Payment API to manage your payments appropriately.

How it works​

Getting a merchant account activated follows these steps:

  1. Onboarding form — Your merchant fills in the Rootline Hosted Onboarding form with their business and identity details.
  2. Company created — Once the form is submitted, a company is created in Rootline. You receive a company.created webhook.
  3. Onboarding review — Rootline reviews the submitted information. You can track progress via the verification_status on the company. See Onboarding Status for details.
  4. Account created — When onboarding is finalized and the merchant is approved, an account is created. You receive an account.created webhook.

Webhooks​

company.created​

When your merchant submits the onboarding form, a company is created. Listen to the company.created (for legal entities that are companies) or person.created (for persons) webhook to know onboarding has started.

Here's an example of a company.created event:

{
    "object": "event",
    "webhook_endpoint_id": "webh_4WxqjT0YfsxXDeKPbrwRie",
    "event_type": "company.created",
    "event_time": "2024-12-24T14:18:11.435566Z",
    "livemode": false,
    "api_version": "2024-04-23",
    "company": {
        "id": "co_5IGIrh15JJZ5oKSYubFpEr",
        "object": "company",
        "name": "TraderJoes",
        "company_name": "Trader Joe's",
        "created_at": "2024-12-24T14:18:11.422Z",
        "reference": "myRefForUser1"
    }
}

account.created​

When Rootline completes the onboarding process and approves the merchant, an account is created. Subscribe to the account.created webhook to be notified.

info

A risk-based onboarding process may apply for your platform, in which case your user might not be required to provide all details from the start, depending on your user's risk profile.

Here's an example of an account.created webhook:

{
    "object": "event",
    "webhook_endpoint_id": "webh_59rz4zUN69BvGY8cpo7lqn",
    "event_type": "account.created",
    "event_time": "2024-12-24T14:21:34.914319Z",
    "livemode": false,
    "api_version": "2024-04-23",
    "account": {
        "id": "acc_47fm2EUbd8ndPcMu5ULmcA",
        "object": "account",
        "description": "Trader Joe's account",
        "name": "simplythetest",
        "legal_entity_id": "co_5IGIrh15JJZ5oKSYubFpEr",
        "base_return_url": "https://www.tradingjoes.com",
        "created_at": "2024-12-24T14:21:34.881Z",
        "reference": "myRefForUser1"
    }
}

Now you're all set to start sending payments to this account.

Configuring webhooks​

To configure webhook events, please read our documentation about webhooks.