Accounts

Account → Accounts is the company and the accounts it holds — “one verification, an account per app or brand.”

Needs organisation.read to see and organisation.write to open an account. Both are held by owner and admin only. Everybody else sees “Only owners and admins can see the organisation.”

Organisation and account

Two words with exact meanings on this page:

• The organisation is the legal entity — the registered company, with its legal name, registration and verification. There is one.
• An account is a business line that takes payments: an app, a brand, a shop. An organisation can hold several.

A software company with two apps is one organisation and three accounts: the company’s own, and one per app. Every account has its own name, account code and statement descriptor, so a customer paying for one app sees that app’s name on their prompt — not the company’s, which they may never have heard of and would dispute.

Every business on PaySigna is already an organisation with one account. Nothing changes for you until you open a second.

What each account keeps to itself, and what is shared

Per account	Shared by the organisation
API keys, webhooks, IP rules	Verification, and the level it reached
Balances, transactions, settlements, withdrawals	Limits that come with the verification level
Settlement destinations	Legal name, registration, tax id, country, address
Pricing in force, channel capabilities	Settlement currency
Statement descriptor, website, what it is paid for
Team, and each person’s role
Going live

Nothing moves between accounts. A balance on one cannot pay a withdrawal on another, and there is no screen that adds two accounts’ figures together. Each account settles to its own destinations.

The accounts list

One row per account in the organisation:

Part	Notes
Name	With a Primary pill on the account that holds the verification.
Account code	Permanent, as on every account.
Status	The account’s own status.
test only	Shown while the account is not yet live.
Your role	Your role in that account, if you have a seat there.
Action	You are here for the account you are in, Open to switch to one you have a seat in, or No seat for one you do not.

No seat is deliberate. Being an owner of one account does not give you access to the others — each account’s team is its own. Ask an owner of that account to invite you; you will accept with your existing password.

Opening an account

Open an account — “for another app or brand of the same company. It opens in test mode straight away; going live is reviewed by PaySigna.”

Field	Required	Notes
Name	Yes	The app or brand customers know, e.g. LoveSync. At least 2 characters.
What it will be paid for	Yes	At least 10 characters, e.g. Monthly subscriptions for the LoveSync app. We read this when the account asks to go live.
Statement descriptor	No	What customers see on their statement or MoMo prompt, up to 22 characters. Defaults from the name.
Website	No	—

What happens when you press Open account:

• You become its owner and primary owner, on your existing sign-in. It appears in your account menu under Switch account straight away.
• The legal identity is copied from the account you opened it from — legal name, business type, registration, tax id, country, address — along with the settlement currency, the pricing plan and the integration mode.
• It opens in test. Switch to it to create test API keys and webhook endpoints; the sandbox works on every channel from the first minute.
• Nothing else is copied. It has no API keys, no webhook endpoints, no settlement destinations and no other team members until you add them. Invite colleagues to it from its own Team page.

Signing up a second business is a different thing

Open an account here when the new line belongs to the same company. A genuinely separate legal entity — a different company with its own registration — signs up on its own at /signup and is verified on its own. You can use the email you already sign in with; see Signing up with an email you already use.

Verification is done once

Verification is of the company, so it is done once, on the primary account, and every account in the organisation shares it. A new account starts at the company’s verification level — no documents to file again — and its live API keys can carry the scopes that level allows.

On any other account, Settings → Verification shows the shared verification, but filing or changing it is refused with a message naming the primary account: “Verification belongs to your organisation and is done once, on account … This account already shares it. Switch to … to update it.” Switch to the primary account to file, update or renew. See Verification.

Limits are shared too

The transaction limits that come with your verification level are counted across the organisation, not per account. If your level allows GHS 50,000 of collections a month, that is GHS 50,000 for all your accounts together — opening a second account does not double it.

Any limit agreed specifically for one account stays that account’s own, and the platform-wide limits apply to each account separately. A payment is refused by whichever limit it would breach first.

Going live, per account

The company’s verification is shared, but what each account sells has not been reviewed. A verified software company opening an account for a betting app is exactly the case review exists for. So each account goes live on its own: when its integration is ready, ask us, and we review its purpose, website and category before switching live on and enabling its channels.

Until then the account’s environment switch stays on Test, and its row on this page says test only.

Switching between accounts

Open on a row, or the account menu (your initials, top right) → Switch account. Either starts a session on that account and ends the one you were in; you are not asked for your password again. See Switching account.