Reseller Owner Portalพอร์ทัลสำหรับเจ้าของผู้แทนจำหน่าย

Who this manual is for

This manual is for the people who run a reseller account in the P2P reseller portal:

• Owners. The founding owner P2P set up when your account was opened, and the co-owners you add yourself (the portal calls them staff). Both have exactly the same rights. You bring merchants to P2P, price them, look after them, and pay your sales agents.
• Sales agents (MDR partners). They sign in to the same portal with a read-only login and see only what they earn. They have their own short manual: the MDR manual.

Your merchants' own staff use the merchant portal, not this one. What they see is in the merchant manual, which is worth having open when a merchant calls you.

Where you sit: between P2P and your merchants

Every baht your merchants' customers pay moves bank to bank. P2P keeps the record, checks slips and matches deposits to withdrawals. It never holds the money. Three things can pass through you:

1. Your commission. Each merchant pays you its fee at the rate you set. You pay P2P its base rate on that merchant's volume. You keep the difference, less what you pay your agents.
2. Merchants' money, sometimes. If your own bank accounts or payment gateway receive a merchant's customers' deposits, that cash belongs to the merchant, and you pay it on.
3. Pool money, if you run a matching pool. Branches that join your pool may pay a buy-in to you, and you settle for them.

What this means for you:

1. Recording a payment in the portal does not send money. Make the transfer in your banking app first, then record it.
2. Figures about who owes whom are for information. P2P does not move that money and cannot see anyone's bank. Nothing is blocked because of them.
3. An agent's share is a percentage of the merchant's volume, not of your margin. Get this wrong and you promise an agent more than you earn. See Your agents' shares.

The whole picture is on one page: How money moves through you.

Your role in five minutes

Your name and role are shown at the bottom of the menu. The menu only lists the pages your login can use.

Login	Who has it	What you can do	What you cannot do
Owner owner	The founding owner, set up by P2P.	Everything in this manual. Some pages also need P2P's merchant creation switch (next section).	Rotate a merchant's API key (the merchant's owner does). Change your own platform base rate, assign merchants to you or take them away, change a merchant's display name, rate limit or active status, set up a custom domain, or undo a settlement payment a merchant has disputed: P2P does these.
Owner staff	Co-owners you add on Staff.	The same as the founding owner, including MDR users, MDR sharing, Branding and Staff.	Reset or switch off the founding owner's login. Only P2P can.
Viewer MDR	Your sales agents, set up on MDR users.	Read their own earnings on My sharing, the merchants they currently earn a share on, the list of groups, and Money without its list of merchants.	Everything else. The dashboard sends them to My sharing, and the report is closed to them.

A few things that are easy to miss:

• A co-owner is a full owner. They can create merchants, set fees, pay merchants, create agents and add more co-owners. Give the role only to people you would trust with the owner's password.
• Every action is recorded against the login that did it. Nobody should share a login.

The merchant creation switch

P2P decides, reseller by reseller, whether you may create and equip merchants yourself. With the switch on, owners also get:

• Create merchant on Merchants;
• Slip providers and Payment gateway under Configuration;
• the whole Manage Bank Account group: Bank accounts, Deposit accounts and Settlement;
• the Gateway and Staff tabs on a merchant's page, and branch staff logins on its Sub-merchants tab.

With the switch off, none of these appear, and there is no message saying why. That is not a fault. Ask P2P platform support if you need it. Every other page in this manual works without the switch.

The menu

Menu group	Pages	Who sees them
Overview	Dashboard	Everyone. An agent is sent on to My sharing.
Merchants	Merchants, Groups, Matching pools	Owners. Agents see the first two, read-only.
MDR management	MDR users, MDR sharing	Owners.
Staff	Staff	Owners.
Configuration	Branding, Slip providers, Payment gateway, Gateway reconcile	Owners. The middle two need the merchant creation switch.
Manage Bank Account	Bank accounts, Deposit accounts, Settlement	Owners, with the merchant creation switch.
Reports	Money, Report, My sharing	Everyone, except Report, which agents do not get.

A number next to Settlement counts the items waiting on you there. It appears once you have opened the Settlement page.

Your own team: co-owner logins

Owner

1. Open Staff.
2. Under Add a staff login, enter Email and Name, then press Create login.
3. Copy the Temporary password at once with Copy. It is shown only this time and it expires after 24 hours. Give it to the person privately, then press Dismiss.
4. On an existing login:
   • Reset credentials clears the password and the authenticator. They set both up again with the new temporary password. A reset does not sign them out: a session they already have open keeps working until they finish setting up again. Use it for someone who is locked out, never to cut someone off.
   • Deactivate cuts the login off at once, including any session already open. There is no button to switch it back on; add a new login instead.

The founding owner's row carries Founding owner and Protected. Only P2P can reset or switch it off.

Agents' logins are made on a different page: see Create an agent's login.

When P2P support works in your portal

Support

A P2P platform admin can open your portal as your reseller, to see what you see when you ask for help. That session is read-only: they cannot change anything. While it lasts, they see a Support session banner reading Read-only — you cannot make changes, with Exit support session. You do not see that banner on your own screens.

What you may notice is a login on Staff whose name ends in "Platform Support". That is the login their session uses. See A "Platform Support" login we never created.

You can do the same for your own merchants: see Act as a merchant.

Sign in

Owner Viewer

You need your email address, your password and an authenticator app on your phone (for example Google Authenticator or 1Password).

1. Open the reseller portal address P2P gave you.
2. Enter your Email and Password, then press Continue.
3. Open your authenticator app and type the code into 6-digit code. Press Verify. The code changes every 30 seconds; if it is about to change, wait for the next one.

Screenshot to comeThe sign-in page, then the 6-digit authenticator code

Your first sign-in

Whoever created your login gives you a temporary password. It works for 24 hours.

1. Sign in with your email and the temporary password.
2. On Set up your account, choose a New password: At least 12 characters, including a letter and a number. Type it again in Confirm new password.
3. Scan the QR code with your authenticator app. If you cannot scan it, type in the secret shown under Or enter this secret manually:
4. Enter the code from the app and press Finish setup.

If the page says Your temporary password has expired. Ask your administrator for a new invite., the 24 hours have passed. Ask for a reset: see I can't get in.

Screenshot to comeFirst sign-in: choose a password and set up your authenticator

Lost your phone, or forgot your password

There is no "forgot password" link. The code page says Can't access your authenticator? Use a backup code., but the reseller portal does not issue backup codes.

• A co-owner can reset you: Staff → your row → Reset credentials.
• The founding owner can only be reset by P2P. Contact P2P platform support.
• An agent is reset by an owner on MDR users.

How this manual is organised

1. Start here: this page.
2. How money moves through you: the fee, your spread, your agents' shares, and whose money you might hold. Read it once.
3. Your merchants: onboarding, fees, groups, settings, branches, matching pools, and acting as a merchant.
4. Your money: dashboard, report, the Money page, agents, and Settlement.
5. Branding and domains: your logo, colours and web address.
6. Rails: slip checking, payment gateway, bank accounts and gateway reconciliation.
7. When something goes wrong: every situation in this manual, symptom first.
8. Glossary.

Something is wrong right now

You are thinking…	Go to
"I can't get past the 6-digit code."	I can't get in
"A page this manual describes isn't in my menu."	A menu or button is missing
"A merchant says a customer's deposit is stuck."	A merchant reports a stuck transaction
"A merchant lost its API key or HMAC secret."	Lost credentials
"The portal refuses the share I want to give my agent."	The share would exceed your spread
"A merchant says I'm holding its money."	A merchant says you are holding its money
"Something else."	When something goes wrong

How to read the pages

• A word in a box, like Create merchant, is a button or label exactly as the portal shows it.
• The badges under each heading say who can do it:
  • Owner means the founding owner and co-owners. They have the same rights.
  • Viewer means an agent's (MDR) login, which is read-only.
  • Support means P2P platform support, in a read-only session in your portal. Where a task also needs P2P's merchant creation switch, the text says so.
• Don't boxes mark actions that can lose money, pay twice or promise more than you earn. Read them before you act.
• The screenshots were taken in Thai. You can switch the portal's language at the bottom of the menu. Your portal shows your own logo and colours, so it may not look like the pictures.

Who to contact

For…	Contact
A co-owner's or agent's login	An owner of your reseller account.
The founding owner's login, the merchant creation switch, your platform base rate, assigning or moving a merchant, a merchant's name, rate limit or active status, a custom domain, undoing a disputed payment	P2P platform support: support@myp2y.com (also shown at the bottom of the sign-in page).
A merchant's integration: webhooks, API key, what its system receives	The merchant's own developer, with the merchant manual's developer appendix.
Your agent's questions about their pay	You. P2P does not pay agents; you do.

When you contact anyone about a payment, send:

1. the merchant (its name and slug) and, for a branch, the branch's code;
2. the deposit or withdrawal ID from the merchant portal, or the merchant order ID;
3. the amount and the time of the bank transfer;
4. a picture of the slip, cropped to the slip only.

The short version

• Money always moves bank to bank. P2P records it, checks it and matches it. It never holds it.
• For each merchant you set a rate, at or above the platform base P2P gives you. The difference is your spread: your commission.
• The merchant pays you its fee. P2P bills you its base on that merchant's volume, and tracks what you owe it on Money.
• You pay your agents (MDR) a share. A share is a percentage of the merchant's volume, taken out of your spread, and the shares on one merchant can never add up to more than your spread.
• If a merchant's customers' deposits land in your bank account or gateway, you are holding that merchant's money. Settlement is where you pay it on.
• Every "owed" figure is for information. Nothing is blocked because of it.

Your commission: rate, platform base and spread

A merchant's activity is counted as volume, and there are two fee types, each with its own rate:

• Pay-in: charged on the money in the merchant's deposits that settled. This is where almost all volume comes from.
• Pay-out: charged when one of the merchant's branches has a withdrawal filled by a deposit from outside that branch. It is usually small, and its rate is usually 0%.

P2P gives you a platform base for each fee type: its own cut, and the lowest rate you may charge. You set each merchant's rate at or above it. An example, for one month of a merchant's deposits:

	Rate	On ฿1,000,000 of deposits	Who pays whom
The merchant's rate	2.50%	฿25,000	The merchant pays you, outside P2P.
P2P's platform base	1.50%	฿15,000	You pay P2P. It appears on Money as what you owe the platform.
Your spread	1.00%	฿10,000	Yours, before your agents' shares.

You find these figures on the Dashboard (this month so far), on each merchant's page, and on the Report. What P2P bills you, and what you have paid it, is on Money.

The floor. The portal will not let you set a rate below your platform base. When you create a merchant, the form shows your base and your margin under each rate as you type, and stops you going lower. Only P2P can change your base.

A merchant with no fee set. A merchant P2P assigns to you may arrive with no rate at all: its page says No fee schedule set. Until you set one, it is billed at P2P's default rate and none of it is yours. See You earn nothing on a merchant.

Your agents' shares (MDR)

An agent (MDR partner) is someone you pay for bringing in merchants. You give them a share on a merchant, or on a group of merchants, for one fee type.

Continuing the example above: the merchant's spread is 1.00%, which is ฿10,000 on ฿1,000,000 of deposits.

You enter	The agent earns	That is…	You keep
0.40	0.40% × ฿1,000,000 = ฿4,000	40% of your spread	฿6,000
1.00	฿10,000	all of your spread	nothing
40	Refused. 40% of the merchant's volume is far more than your 1.00% spread.

So to give an agent 40% of your margin on this merchant, enter 0.40, not 40.

The rules the portal applies:

• The cap. On one merchant, for one fee type, all your agents' shares together may not exceed your spread. A share that would is refused with This share would exceed the remaining reseller spread for this merchant. For a share on a group, every merchant in the group is checked, and one merchant with too small a spread refuses the whole share.
• Merchant beats group. A share you set on a merchant replaces that agent's group share for that merchant.
• The whole merchant. A share covers all of the merchant's volume, its branches included. There is no share on a single branch.
• Dated. A share starts on its effective date (Bangkok time). To end it, give the same agent 0% from the day it should stop.
• You pay your agents, outside P2P. The portal works out what each agent earned; it does not pay them and records no payment to them.

How to set shares: Give an agent a share.

Whose money you might hold

When a merchant's customer deposits, P2P chooses where the money goes, in this order:

1. to a customer of the merchant (or of a merchant sharing a pool with it) who is withdrawing, if a match is possible;
2. to the merchant's own accounts and gateway, or its branch's own accounts;
3. to your reseller bank accounts and gateway, only where P2P has switched routing through resellers on, and only once the merchant's own accounts and gateway cannot take the deposit;
4. to P2P's own accounts, only if P2P has switched that fallback on for the merchant.

Money that lands in one of your accounts belongs to the merchant, or to its branch. You are holding it for them:

• Settlement lists it, merchant by merchant, under You owe. You transfer it to them and record the payment. See Settlement.
• Money shows it as Custody — cash you hold downstream, next to what you owe P2P, and never added to it.
• Deposit accounts shows, for each of your accounts, what came in and what you have recorded going out.

Whether routing through resellers is switched on is set by P2P, not in this portal. Before you promise a merchant that your accounts will catch its deposits, ask P2P platform support. See A bank account or gateway never receives deposits.

Matching pools you own

A matching pool decides whose customers can be matched with whose. The branches of one merchant usually match each other already, through the merchant's own pool; a branch shown as isolated matches only its own customers. If you own a pool, branches of different merchants of yours that join it can be matched with each other too, so one merchant's depositors can pay another merchant's withdrawing customers.

Owning a pool has consequences:

• You settle for its members. When one member's customer is paid with another member's money, the records show who owes whom, and you are the party in the middle.
• Members may pay you a buy-in before they join, if you tick that when you create the pool. The buy-in is their money, held by you.
• The buy-in becomes their withdraw allowance. A branch's withdraw allowance is what lets its withdrawals be filled with other people's money. For a fill from another merchant's deposit it is always checked. See The withdraw-allowance limit.
• Members tell you what they paid. A member files a notice ("paid back", "sent a buy-in", "wants a buy-in back"), and nothing changes until you confirm it. See Pool notices.

How to create and run pools: Matching pools.

What the figures are, and what they are not

Your two positions are kept apart everywhere, and are never added together:

Position	What it is	Where
The fee	What you owe P2P: its base on your merchants' volume, less what you have paid.	Money
Custody	Merchants' money that landed in your accounts, less what you have paid on.	Money and Settlement

What your merchants owe you (their fee at your rate), and what you owe your agents, are settled between you and them. The portal reports the figures; it keeps no balance for them.

Who to ask. P2P platform support, if a figure looks wrong after a refresh.

Your merchant list

Owner Viewer

Merchants lists every merchant in your book, with Status, Pay-in rate, Pay-out rate, MTD usage and MTD fee (this month so far). Press View to open one.

A merchant joins your book when you create it, or when P2P assigns it to you. Only P2P can move a merchant to another reseller or take it off your book. An agent sees only the merchants they currently earn a share on.

Onboard a new merchant

Owner

This needs P2P's merchant creation switch. Without it there is no Create merchant button; ask P2P to create the merchant and assign it to you, then start at step 3.

The checklist, in order:

1. Create it, with the data processing agreement accepted.
2. Copy its API key and HMAC secret and hand them to its developer.
3. Give it somewhere for customers to pay.
4. Allow its checkout's return address.
5. Give the merchant an owner login.
6. Check its fee and settings.

1. Create it

1. Merchants → Create merchant.
2. Fill in:
   • Slug: 3–64 chars, lowercase letters, numbers and hyphens. It is the merchant's permanent short name, and it appears in its customers' usernames. It cannot be changed from this portal, so agree it with the merchant first.
   • Display name: the name its staff and your reports show.
   • Webhook URL (HTTPS): the address the merchant's system receives notifications at. Its developer gives you this.
   • Pay-in rate and Pay-out rate: what the merchant pays you. You set what the merchant pays. The platform keeps its base rate; the rest is your margin.
3. The live floor check. As you type a rate, the line under it shows your platform base and your margin, for example "Platform base 1.50% · your margin 1.00%". If a rate is below your base, the line turns red and says so, and Create merchant stays greyed out until you raise it.
4. Tick I accept the platform Data Processing Agreement on behalf of this merchant. and enter the DPA version. The merchant goes live (Active) only when the DPA is accepted; otherwise it is created Suspended.
5. Press Create merchant.

The merchant is added to your book straight away, with the two rates you entered.

2. Copy the API key and HMAC secret

The page now says Merchant created. Copy the API key and HMAC secret now — they are shown only once and cannot be retrieved later.

1. Press Copy next to API key, and again next to HMAC secret.
2. Give both to the merchant's developer through a secure channel.
3. Press View merchant to carry on.

If instead the page says This merchant already exists — its credentials were issued when it was first created and cannot be shown again. Rotate the API key and HMAC secret from the merchant's detail page to obtain new ones., that slug already existed: you created the same merchant twice. No new keys were made. There is no rotate button on a merchant's page in this portal; the merchant's owner rotates them. See Lost credentials.

3. Give it somewhere for customers to pay

This merchant cannot take payments until a payment rail (gateway) is attached. A new merchant has no bank account or gateway of its own. Any one of these fixes that:

• Register its payment gateway on its Gateway tab (below).
• Its owner adds bank accounts or a gateway in the merchant portal (see Bank accounts in the merchant manual).
• Your own bank accounts or gateway can catch its deposits, but only where P2P has switched routing through resellers on, and only when its own accounts cannot take them. See Rails.

Matching one customer's deposit to another's withdrawal is not a substitute: it only works while a withdrawal is waiting.

4. Allow its checkout's return address

1. The merchant's page → Matching & Config → Hosted-checkout return domains.
2. In Registered domains, enter the merchant's website addresses. One host per line — no https://, port, or path. Registering a domain also authorises its subdomains.
3. Press Save.

Until at least one is saved, the page warns No domains registered — hosted checkout is disabled for this merchant until at least one is added.

5. Give the merchant an owner login

This needs the merchant creation switch. Without it, ask P2P to create the login.

1. The merchant's page → Staff → Add a staff login.
2. Enter Email and Name, choose Owner (full access) as the Role, and press Create login.
3. Copy the Temporary password with Copy. Copy it now — it is shown only once and cannot be retrieved later. Give it to the person privately.

The owner then signs in, sets up their authenticator, and invites the rest of their team themselves. Only the merchant's owner can rotate its API key.

6. Check its fee and settings

1. On the merchant's Overview, check Fee schedule history lists both rates.
2. On Matching & Config, check the amounts it offers, its payment window and its routing (Matching & Config).
3. If the merchant has branches, set them up on Sub-merchants (Branches).

A merchant's page

Owner Viewer

The header shows the merchant's name and slug, Act as merchant (owners), and its status as the portal stores it: ACTIVE, or SUSPENDED when it cannot take new payments.

Tab	What is on it	Who sees it
Overview	Usage report, Fee schedule history, Sub-merchants, and Set fee.	Everyone. Agents do not get Set fee.
Matching & Config	Webhook, checkout return addresses, amounts, payment window, routing, partial fills, priority tiers.	Owners.
Billing	Usage credit, adjustments, top-up requests.	Owners.
Sub-merchants	The withdraw-allowance limit and the merchant's branches.	Owners.
Gateway	The merchant's own payment gateway.	Owners, with the merchant creation switch.
Staff	The merchant's back-office logins.	Owners, with the merchant creation switch.

Set or change a fee

Owner

1. The merchant's Overview → Set fee.
2. Choose the Fee type: Pay-in or Pay-out.
3. Enter Rate (%): 2.5 means 2.50%.
4. Choose Effective from (YYYY-MM-DD) (a Bangkok date). You can pick a future date to schedule a change.
5. Add a Note (optional) if it helps, and press Set fee.

It appears in Fee schedule history. Each day is priced at the rate in force on that day. This form has no live check: a rate below your platform base is refused when you save it (Rate refused).

Groups

Owner Viewer

A group is a set of your merchants, for pricing them together and for giving an agent a share on all of them at once. Agents see the list of groups, read-only.

1. Open Groups. Type a name and press Create group.
2. Under Members, pick a merchant in Add merchant and press Add.
3. To price every member at once, use Bulk fee: the fee type, Rate (%), Effective from and an optional note, then Apply to all members.

What the bulk fee does: it writes the same rate onto each merchant in the group at that moment, as if you had set it on each one. It is all or nothing: if the rate is below your base, no merchant is changed. A merchant you add to the group later keeps its own rate until you apply the fee again.

What a group cannot do yet:

• You cannot see or remove its members. The page shows only how many there are. Keep your own list; to take a merchant out, ask P2P platform support.
• A group that has ever carried an agent's share cannot be deleted. Delete group fails with an error. Set its shares to 0% and stop using it instead.

Matching & Config

Owner

These are the same settings the merchant's owner sees under Settings in the merchant portal; either of you can change them. Each block has its own save button. What each one does is explained in the merchant manual's Matching and routing.

Block	What you set
Profile	Update this merchant's webhook URL. Display name and rate limit are managed by P2P admin.
Hosted-checkout return domains	Where the payment page may send customers back to. None means no hosted checkout.
Denomination subset	Untick amounts the merchant should not offer. At least one must stay ticked.
Deposit reservation window	Between 5 and 30 minutes. Leave blank to use the platform default.
Deposit cascade routing	Rail order (Round robin, Gateway first, Bank first) and P2P match cutoff (THB): Above this amount, skip P2P matching and go straight to gateway/bank.
Allow partial fulfillment	Whether withdrawals from this merchant's pool may be filled by multiple deposits.
Priority tier thresholds	Saved now, but they only take effect once P2P switches withdrawal priority on.

Screenshot to comeA merchant's Matching & Config tab

Billing: usage credit and top-ups

Owner

Usage credit is the merchant's prepaid balance with P2P. It goes down as its customers' deposits settle, and can go below zero (see the merchant manual's Overdraft).

1. The merchant's page → Billing. Balance shows where it stands.
2. A top-up request from the merchant: under Top-up requests, check the Amount and Bank ref against the payment. Press Approve to credit it, or Reject with a reason the merchant will see.
3. A correction with no request: under Adjust balance, choose Credit or Debit, enter Amount (THB) and a Reason, and press Adjust balance.
4. History lists every request and every change.

Screenshot to comeA merchant's Billing tab: balance, adjust, top-up requests

The merchant's payment gateway

Owner

This needs the merchant creation switch.

1. The merchant's page → Gateway → Register a PGWAY gateway.
2. Enter the API key and API secret from the gateway provider, and optionally a Label (optional) and Base URL (optional). Press Register gateway. The secret is never shown again.
3. Use Activate or Deactivate on its row.
4. The provider must know where to report payments. This tab does not show that address. The merchant's owner finds it as the Callback URL on their own Payment gateways page (see the merchant manual's Register and switch on a gateway) and pastes it into the provider's settings. Until then, deposits and payouts through the gateway sit unfinished.

The merchant's staff logins

Owner

This needs the merchant creation switch. Staff lists the merchant's back-office logins. You can add one (as above) or press Reset credentials on one. A reset clears the password and the authenticator and signs the person out, though a page they already have open can keep working for a short while; copy the new temporary password it shows.

You cannot change a login's role or switch it off here. The merchant's owner changes roles on their Team page; for someone who has left, see Someone has left.

Act as a merchant

Owner

When a merchant calls about a stuck deposit or withdrawal, you can open its portal and see exactly what its staff see.

1. The merchant's page → Act as merchant.
2. Enter a Reason for access. Recorded on the audit trail. At least 8 characters.
3. Choose the Session type:
   • Read-only — see what their staff see, change nothing
   • Support write — also unstick transactions (fulfil a withdrawal, request a cancel, retry a webhook)
4. For support write, enter Your authenticator code: the code from your own authenticator.
5. Press Start session. The merchant portal opens in a new tab, with a Support session banner on every page. The session lasts 15 minutes and cannot be extended; press Exit support session when you are done.

What a support-write session can and cannot do is listed in the merchant manual: When P2P support or your reseller works in your portal. In short, it can record a withdrawal payment, request a cancellation and retry webhooks. It can also add, change and reset the merchant's staff logins and change a few matching settings, so treat it with the same care as the merchant's owner login. It cannot approve or reject slips, close a withdrawal to new deposits, add or change bank accounts or gateways, or rotate keys.

The merchant sees what you did under a staff login whose name ends in "Platform Support" (see the merchant manual's support staff member). Every action names you.

Screenshot to comeThe "Act as this merchant" dialog: reason, session type and your code

Branches (sub-merchants)

Owner

A branch is part of a merchant with its own customers and staff, and its own usage credit and withdraw allowance. How branches work, from the merchant's side, is in the merchant manual's Branches and your team. Everything below is on the merchant's Sub-merchants tab.

The withdraw-allowance limit

Sub-merchant withdraw allowance limit decides when a branch's withdraw allowance is checked. It has two states, and neither of them is "off":

State	What is checked
Enforced on every fill	Every fill of a branch's withdrawal, including fills from the same merchant's deposits.
Cross-merchant fills only	Only fills from another merchant's deposits.

A fill from another merchant is always checked, whatever you choose, because there the shortfall would be settled with another business's cash. Switch with Enforce on every fill or Enforce on cross-merchant fills only.

There is no longer a switch that keeps a branch apart from its sister branches. That now depends only on its matching pool (below).

Create and manage a branch

1. Enter an External code (the code the merchant's system sends with the branch's transactions; agree it with its developer) and a Display name, and press Create.
2. Press Manage on a branch's row. The panel has:
   • Usage credit balance: enter an amount and a reason, then Allocate or Deallocate.
   • Withdraw allowance: enter an amount and a reason, then Grant allowance or Claw back.
   • Settings: Save name, Suspend, Reactivate or Deactivate.
   • Matching pool (next section) and, with the merchant creation switch, Staff.

While a branch is suspended or deactivated, the merchant's system cannot start new deposits or withdrawals for it.

A branch's matching pool

The Matching pool block shows the branch's pool and how many members it has, or Isolated when it matches only its own customers. Cash held by lists who is holding the branch's cash.

• Admit an isolated branch to one of your pools: pick one in Choose one of your pools… and press Admit to pool. For a pool marked paid, enter Buy-in received (THB) and Reason (audit), and press Record buy-in and admit. Only once the branch's money has arrived in your account.
• Take a branch out of your pool: Remove from pool. Removes this sub-merchant from your pool. It keeps trading, but only with its own customers until it joins a pool again. It is refused while the branch owes the pool money.
• A branch in a pool you do not own shows Removing a sub-merchant from a pool is done by the merchant, or by an administrator.

A branch's staff

This needs the merchant creation switch. Logins scoped to this sub-merchant. Operators can review its slips and fulfil its withdrawals; viewers are read-only.

1. In the branch's panel under Staff, enter the person's email and name, choose Operator or Viewer (read-only), and press Invite.
2. Copy this now — it is shown once and cannot be retrieved again. Give it to them privately.
3. On a login: Reset credentials or Suspend.

What a branch login can do is in the branch staff manual.

Matching pools

Owner

Read Matching pools you own first. Grouping sub-merchants into separate pools does NOT change who matches whom. Every pool you own gives its members the same reach, so members of two of your pools still match each other. Pools are a reporting and settlement grain — owning one is what makes you the party that settles for its members.

1. Open Matching pools.
2. To add a pool, under Create a pool enter a Pool name, choose Who owns this pool (You (a pool you own) or A merchant you own), tick Members must buy in before joining if members must pay in first, and press Create pool. The new pool starts disabled and will not become your default. Enable it once you are ready to carry settlement for its members.
3. Press Enable or Disable on a pool, and confirm in the dialog.
4. Rename changes a pool's name. A merchant's own default pool shows Merchant default — read-only
5. Admit branches from each merchant's Sub-merchants tab (A branch's matching pool).

Screenshot to comeThe Matching pools page: your pools, members, buy-in and state

When something goes wrong with a merchant

A new merchant can't take payments

Owner

What you see. The merchant shows Inactive in your list and SUSPENDED on its page. Or its Gateway tab says No payment gateway registered yet — this merchant cannot take payments until one is added. Or its customers are told they cannot start a deposit, or its payment page refuses to open.

Why it happens. One of the onboarding steps is missing. The agreement box was left unticked, so the merchant was created suspended. Or it has no bank account or gateway to receive deposits. Or no checkout return address is saved, so hosted checkout is off. Or its gateway is registered but switched off, or the provider does not have the callback address.

What to do

1. Suspended: ask P2P platform support to make it active, once the merchant has accepted the data processing agreement. You cannot change its status here.
2. Nowhere to pay: register its gateway and switch it on (Gateway tab), or ask its owner to add bank accounts in the merchant portal.
3. Checkout off: Matching & Config → Hosted-checkout return domains → add the merchant's website → Save.
4. Gateway deposits never finish: ask the merchant's owner to paste the Callback URL into the provider's settings.
5. If customers still see an error, send the merchant's developer to the merchant manual's Customers can't start a deposit.

Who to ask. P2P platform support, to activate a merchant.

A merchant lost its API key or HMAC secret

Owner

What you see. The merchant's developer has lost the API key or the HMAC secret. Or, creating a merchant, the page says This merchant already exists — its credentials were issued when it was first created and cannot be shown again. Rotate the API key and HMAC secret from the merchant's detail page to obtain new ones.

Why it happens. Both are shown once, when the merchant is created. P2P cannot show them again. Despite what that message says, this portal has no rotate button: only the merchant's owner can issue new ones, in the merchant portal.

What to do

1. Ask the merchant's owner to sign in to the merchant portal and rotate the key or the secret (see the merchant manual's Rotate the API key and Rotate the signing secret).
2. If the merchant has no owner login yet, create one: Staff → Owner (full access) (Give the merchant an owner login).
3. If the owner is locked out: Staff → their row → Reset credentials, and give them the new temporary password.
4. Without the merchant creation switch, ask P2P platform support to do step 2 or 3.

Who to ask. The merchant's owner; P2P platform support if nobody can sign in.

A merchant's top-up is waiting, or its usage credit is below zero

Owner

What you see. A merchant says its top-up has not arrived. Its Billing tab lists the request under Top-up requests with Approve and Reject. Or the balance is below zero.

Why it happens. A top-up changes the balance only when someone approves it: you, or P2P. Usage credit below zero does not stop the merchant's deposits or withdrawals; it is a debt to settle.

What to do

1. Check that the payment the request describes has arrived, using its Bank ref and Amount.
2. If it has, press Approve. If not, press Reject and say why; the merchant sees your reason.
3. For credit you have agreed without a request, use Adjust balance.
4. A branch's credit comes from its merchant: Create and manage a branch.

Who to ask. P2P platform support, about credit terms.

A branch's withdrawals are refused, or never get matched

Owner

What you see. A merchant says its system's requests to create withdrawals for one branch are refused for "insufficient withdraw allowance". Or a branch's withdrawals wait while deposits keep arriving.

Why it happens. A branch in a matching pool that needs one must hold enough withdraw allowance. It is held when the withdrawal is created, and checked again when it is matched. For a match inside the same merchant, that second check follows the withdraw-allowance limit. For a match with another merchant it always applies.

What to do

1. The merchant's Sub-merchants tab → the branch → Manage → Withdraw allowance.
2. If the branch has paid in, enter the amount and a reason and press Grant allowance.
3. Check the branch's Matching pool. A branch in a paid pool gets its allowance from its buy-in.
4. Once topped up, the merchant's system creates the refused withdrawal again. A stuck one can be paid by the merchant's own staff.
5. If the allowance seems to have been charged twice for a withdrawal the merchant's staff paid by hand, report it to P2P platform support before you top it up. The merchant manual describes this known problem in A sub-merchant's withdrawal is refused.

Who to ask. The merchant's owner, then P2P platform support.

Someone has left, or is locked out

Owner

What you see. A co-owner, an agent, a merchant's staff member or a branch login needs cutting off, or its owner cannot sign in.

Why it happens. Each kind of login is switched off in a different place, and some only by P2P.

What to do

1. Your co-owner: Staff → their row → Deactivate. It takes effect at once.
2. Your agent: see An agent has stopped working with you.
3. A branch login: the merchant's Sub-merchants tab → the branch → Staff → Suspend.
4. A merchant's head-office staff: Staff → their row → Reset credentials, and do not pass on the new password. That stops them signing in again. Then ask the merchant's owner to suspend the login on their Team page (see the merchant manual's Suspend a login); if the person was an owner, ask P2P to switch the login off.
5. A merchant owner who is locked out: the same Reset credentials, and give them the new temporary password.

Who to ask. P2P platform support, to switch off a merchant's head-office login or your founding owner's.

Read How money moves through you first. This chapter is the screens and the steps.

Where each figure lives

You want to know…	Open
How this month is going	Dashboard
Each merchant's fee and your spread, for any period	Report
What P2P bills you, and what you have paid it	Money
What your agents earned	MDR sharing
Merchants' money you are holding, and paying it on	Settlement
What came into each of your bank accounts	Deposit accounts (Rails)

The dashboard

Owner

Dashboard opens on this month so far:

• Assigned merchants and Active merchants.
• MTD gross spread: your spread on all your merchants' volume.
• MTD platform base paid: P2P's base on that volume, as worked out from the rates. What you have actually paid P2P is on Money.
• Your MTD net: your spread less your agents' shares.
• Top merchants by MTD volume, and Quick links.

Below them, Deposit & withdrawal flow shows your merchants' deposits and withdrawals over a range you choose: counts, a chart, the amounts customers use, how fast withdrawals are paid, and a table per merchant. The page refreshes itself every 30 seconds.

An agent who opens the dashboard is sent to My sharing instead.

The report

Owner

1. Open Report. Choose From and To and press Apply. Dates are GMT+7, and the last day is included.
2. Totals shows Total usage, Merchant fee (what your merchants owe you at your rates), Platform revenue (P2P's base) and Reseller gross (your spread).
3. Per-merchant breakdown gives the same per merchant; press ▸ on a merchant with branches to see By sub-merchant. Direct (no sub-merchant) is activity not tagged to any branch.

Invoice each merchant from its Merchant fee. The report is for owners and co-owners only: it shows every agent's share, so agents get This report covers the whole reseller — the fee waterfall and every MDR's share — so it is available to owners and staff only.

The Money page

Owner Viewer

What your merchants generated, what you owe the platform, and what you hold for them. It has three parts:

1. Incoming. Billable activity across your merchants. Every settled deposit and every withdrawal fill is billable, whatever route it took. Per merchant: Events, Volume, Fee accrued and Billed to you. A merchant marked No longer yours has left your book but was billed to you in the past. Highlighted rows were billed to you for only part of the period — the rest went to the platform directly, on days the merchant was not assigned to you. Invoice from the “Billed to you” column, not from “Fee accrued”.
2. Balance. These are two separate accounts. They are never added together — one is what you owe the platform, the other is cash you are holding for others.
   • Fee — what you owe the platform: accrued − paid = outstanding. The platform bills one party per merchant. For merchants assigned to you, that party is you — not them.
   • Custody — cash you hold downstream: accrued − settled = owed. Deposits that landed in your bank pool and are owed onward. Not yours.
3. Outgoing. The payments to P2P that P2P has recorded from you, each Recorded, Disputed or Void. Only Recorded payments are counted in the Paid figure above. Disputed and Void amounts stay listed as a record of what was claimed, and are still part of the Outstanding figure above. Settled downstream totals what you have recorded paying on to merchants and branches.

Paying P2P. Transfer what you owe as your agreement with P2P says. P2P records the receipt, and it appears under Outgoing. If you do not recognise one, see A fee payment you don't recognise.

An agent sees this page without the per-merchant list, and without Dispute.

Your agents (MDR)

Create an agent's login

Owner

1. Open MDR users. Under Create MDR user, enter Email and Display name, and press Create MDR user.
2. Temporary password — save this now. This password will not be shown again. Share it securely with the user. Press Copy, then Dismiss. It expires after 24 hours.
3. Send the agent the MDR manual. They sign in at the same address as you.

On an existing agent:

• Reset password issues a new temporary password and clears their authenticator, so they set both up again. It does not sign them out of a session already open, so never use it to cut an agent off.
• Deactivate stops them signing in. There is no button to switch them back on. It does not end their shares: see An agent has stopped working with you.

A new agent sees nothing until you give them a share.

Give an agent a share

Owner

Read Your agents' shares first: the share is a percentage of the merchant's volume.

1. Open MDR sharing. Under Assign share:
   • MDR user: the agent.
   • Fee type: Pay-in or Pay-out. A share covers one fee type; give two shares for both.
   • Scope: Single merchant or Merchant group, then pick it.
   • Share (%): the percentage of the merchant's volume. 0.40 means 0.40%. Set to 0 to remove the share.
   • Effective from (YYYY-MM-DD).
2. Press Assign share. The page says Share assigned., or refuses it (see The share would exceed your spread).

To change a share, assign it again with the new percentage and date. The old one applies up to that date.

See what your agents earned

Owner

1. On MDR sharing, below the form, choose From and To and press Apply. Without dates it shows this month so far.
2. The table lists each agent's shares: Merchant, Fee type, Share (%) and Share (THB) for the period.
3. Pay each agent what you agreed, outside P2P. The portal records no payment to agents.

My sharing shows the same rows, with totals and a day-by-day breakdown when you press a row. For an owner it lists every agent's rows but does not name the agent, so use MDR sharing to tell them apart.

Settlement: paying merchants what you hold

Owner

This page needs P2P's merchant creation switch. It matters when merchants' deposits land in your own accounts (Whose money you might hold).

Settlement is about people, not bank accounts. It is headed with your reseller's name. At the top:

• "as of" a date: the figures under You owe are a snapshot. The ⟳ button (Refresh) takes a fresh one; it works about once an hour.
• What can I do?: what your login can do here, and what only others can.

Tab	What it holds
Balances (opens first)	Find merchant… to search. You owe: grouped under each merchant's name, one row for Direct (the merchant itself) and one per branch, as Deposits, Buy-in or Pool. Owed to you: only pool money another merchant's branch owes back through a pool you own; usually empty.
To do	Needs you: merchants asking to be paid, payments they disputed, and notices from pool members. Waiting on them: payments you recorded that they have not yet confirmed.
History	What you have paid, grouped by who you paid, with the slips.
Payout accounts	Nothing for a reseller: Nobody owes a reseller money here, so there is nothing to ask for.

At the bottom, Platform fees due ฿… shows the platform's fee on these positions on its own line. It is never added to the rows above. What you yourself owe P2P is on Money ›

A reseller is never the one asking to be paid here, so Request payout, It arrived and Dispute are not yours.

Pay a merchant and record it

1. Transfer the money in your banking app first. Recording it does not send anything.
2. Find the row:
   • if the merchant asked, To do → Pay … → Record payment;
   • otherwise Balances → You owe → the merchant or branch → Record payment. A row the merchant asked about shows Requested …
3. Fill in:
   • Amount (before fee): the full amount you are clearing, before any fee. It starts filled in with everything you owe this party. If you paid less, change it.
   • Fee you keep: only if your agreement lets you keep your fee out of this payment. You transfer is then worked out for you; check it against your slip.
   • Paid from, when the form offers it: which of your accounts it left.
   • Date paid, and where you sent it (bank, last 4 digits and account name). When the merchant asked, their account is filled in: check it is where you really sent it.
   • Bank reference (optional) and Wire slip. The slip is optional, but without one nothing can catch the same transfer being recorded twice.
4. Press Record payment. When nobody had asked, the form is much the same (it can also offer the merchant's registered accounts to pick from) and its button reads Record payment.
5. The payment moves to Waiting on them until the merchant confirms it arrived, and it is listed under History.

Screenshot to comeThe "Record payment" drawer: amount before fee, fee you keep, paid from, destination and slip

Fix a payment you recorded

• Recorded by mistake, or with the wrong figure: History → the payment → Void this. Give a reason (the merchant is shown it) and press Void. What you owe goes back up. Then record the correct payment.
• The merchant disputed it: see A settlement payment is wrong.

Pool notices from your members

If you own a matching pool, its members cannot record pool money themselves. They file a notice, and you decide it under To do → Needs you:

The notice reads	Confirming records…
… says they paid back	their payment to the pool, and gives them that much withdraw headroom back.
… says they sent a buy-in	their buy-in, which becomes their withdraw allowance.
… wants a buy-in back	that you returned their buy-in.

1. Press Confirm or Decline on the row. A drawer shows what they say and when they filed it.
2. Check your bank statement before you confirm. For a buy-in they want back, transfer it first.
3. Confirm, or decline with a reason; they are shown it. Confirming is what moves the money. A decision is final — if it turns out wrong, correct it with a new entry.

Cells marked "Soon"

A few pool actions are not open on this page yet. Their cells are greyed out with a reason:

• Buy-in → Return: Returning a buy-in is not open on this page yet. On a Direct row it says A buy-in held at merchant level is not returned here — it comes back when the merchant asks for it.
• Pool → Pool payment: Recording a pool payment is not open on this page yet.
• Received on an Owed to you row does not open anything yet.

Until they open, a member's notice is the way: ask the branch to file it, and confirm it. See A pool member's notice, or a cell marked "Soon".

When something goes wrong with money

The share would exceed your spread

Owner

What you see. MDR sharing refuses a share with This share would exceed the remaining reseller spread for this merchant.

Why it happens. On one merchant, for one fee type, all your agents' shares together may not be more than your spread there (the merchant's rate minus your platform base). Common causes:

• You entered a share of your margin, not of volume: 40 instead of 0.40.
• Other agents already hold shares on that merchant.
• The spread is zero: the merchant has no fee set, its rate equals your base, or (for pay-out) both are 0%.
• For a group: one merchant in the group has too small a spread, which refuses the whole share.

What to do

1. Work out the share as a percentage of volume: Your agents' shares.
2. On the merchant's Overview, read Fee schedule history. Your platform base is shown under the rates on Create a merchant, or ask P2P.
3. On MDR sharing, add up the shares other agents already hold on that merchant for that fee type.
4. To make room, lower another agent's share from a date, or agree a higher rate with the merchant and set it. For a group, give shares merchant by merchant instead.

Who to ask. P2P platform support, if your platform base looks wrong.

You earn nothing on a merchant

Owner

What you see. A merchant has volume but Reseller gross is ฿0 on the Report. Its Fee schedule history says No fee schedule set. Or Money marks it No longer yours or highlights its row.

Why it happens.

• No fee set. A merchant P2P assigned to you can arrive without one. It is then billed at P2P's default rate, and all of it goes to P2P.
• Rate equal to your base. Your spread is zero.
• Pay-out is usually 0% on both sides, so it earns nothing unless you set a rate above your base.
• The merchant was not yours for part of the period. For those days P2P billed the merchant directly.

What to do

1. Set a fee from today.
2. For past days, ask P2P platform support. Don't back-date the fee yourself: it changes your reports but not what P2P has billed.
3. If a merchant was moved off your book by mistake, ask P2P. Only P2P assigns merchants.

Who to ask. P2P platform support.

An agent has stopped working with you

Owner

What you see. An agent has left, or you no longer pay them.

Why it happens. Switching off an agent's login and ending their shares are two separate steps. Deactivate only stops them signing in. Their shares keep counting against your spread, keep taking room under the cap, and keep lowering Your MTD net.

What to do

1. On MDR sharing, note every merchant or group and fee type the agent holds.
2. For each one, assign the same agent 0 from the day they stop.
3. On MDR users, press Deactivate on their row and confirm.
4. For their final payment, set the period on MDR sharing and read what they earned.

Who to ask. Nobody: this is yours to do.

A merchant says you are holding its money

Owner

What you see. A merchant or branch says its customers' deposits went to your account and asks to be paid. To do shows Pay … with Requested …, or You owe lists Deposits for it.

Why it happens. When a merchant's own accounts could not take a deposit, it was sent to yours. The money is theirs, and they have asked for it.

What to do

1. Check Deposit accounts: which of your accounts received it (Rails).
2. Press ⟳ on Settlement if the "as of" date is old.
3. Transfer the money, then record it: Pay a merchant and record it.

Who to ask. P2P platform support, if the figure looks wrong after a refresh.

A settlement payment is wrong: disputed, or recorded by mistake

Owner

What you see. To do shows … disputed with the merchant's reason. Or you recorded a payment with the wrong amount, or one you never sent. Or recording fails with This slip has already been used for another payment. Each wire can only be recorded once.

Why it happens. You record, the merchant checks. Nothing checks the amount you type. The merchant's only check is a dispute, which puts the amount straight back as owed. You can void your own payment until it is disputed; after that, only P2P can undo it.

What to do

1. Your mistake, not yet disputed: void it and record the correct payment.
2. Disputed: check your bank records. If you paid, but a different amount, press Record again on the row and record the right figure. If you paid in full and the merchant is wrong, talk to the merchant. To undo the disputed record, ask P2P.
3. Slip already used: that transfer is already recorded. Don't record it again.

Who to ask. P2P platform support, to undo a disputed payment.

A pool member's notice, or a cell marked "Soon"

Owner

What you see. Needs you lists … says they paid back, … says they sent a buy-in or … wants a buy-in back. Or a You owe row's Return or Pool payment is greyed out as "Soon".

Why it happens. In a pool you own, members cannot record pool money; they tell you, and confirming records it. Returning a buy-in and recording a pool payment directly from the Balances rows are not open yet.

What to do

1. Check your bank statement against the notice.
2. For a buy-in the member wants back, transfer it to them first.
3. Press Confirm, or Decline with a reason (Pool notices).
4. For a greyed-out row, ask the branch to file the matching notice, then confirm it.

Who to ask. P2P platform support, if a member cannot file its notice.

The Money page doesn't match your invoices

Owner

What you see. The fee ledger has not been opened yet, so nothing is being billed. This is not a zero balance. Or a merchant's Fee accrued differs from its Merchant fee on the report. Or rows are highlighted, or marked No longer yours.

Why it happens. The two pages answer different questions. Fee accrued is what P2P bills on that merchant: its base for days the merchant was yours, and the merchant's full rate for days it was not. Merchant fee is what the merchant owes you at your rate. A highlighted row was yours for only part of the period. Until P2P opens its fee ledger, nothing is billed and the figures are not a zero balance.

What to do

1. Invoice merchants from Merchant fee, only for the days they were yours.
2. Pay P2P from Outstanding.
3. Ask P2P platform support when billing starts, or about a merchant you think was moved by mistake.

Who to ask. P2P platform support.

A fee payment you don't recognise

Owner

What you see. Outgoing lists a Recorded payment you did not make, or with the wrong amount.

Why it happens. P2P records your fee payments. Recording a receipt reduces what you owe. If you do not recognise this payment, contest it — the amount returns to your outstanding balance until an admin resolves it. A reason is required.

What to do

1. Check your bank statement.
2. On the row, press Dispute, say why in the box, and press Submit dispute. The row shows Disputed.

Who to ask. P2P platform support.

Your logo and colours

Owner

1. Open Branding. Customise the colours and logo shown to your merchants and their customers.
2. Colours: enter Primary colour and Accent colour as six-digit hex codes, for example #1A6B4F. Press Save colours.
3. Logo: under Upload logo, choose a file (JPEG, PNG or WEBP — max 5 MB.) and press Upload. Current logo shows the one in use.
4. Preview shows how the colours look together before anyone else sees them.

Colours and logo are saved separately: saving one does not change the other.

Where your brand appears

Your logo and colours are shown on:

• your reseller portal, for you, your co-owners and your agents;
• your merchants' portal, for their staff and branch staff;
• the payment page your merchants send their customers to (the hosted checkout).

Three rules decide what a given screen shows:

1. A merchant's own colours win. If P2P has set colours for one merchant, that merchant shows its own, not yours.
2. Only merchants in your book. A merchant P2P has moved off your book goes back to P2P's look at once.
3. Anything missing falls back to P2P's look. A page never fails to open because of branding.

Your brand does not reach a merchant's own website or app, only the P2P pages they send customers to. On your own web address (below) the sign-in pages take your colours and icon, but they still show the P2P name and P2P's support contact.

Branded API docs for your merchants

Share this branded API reference with your merchants — it shows your logo and colours over the same Partner API.

1. On Branding, find Partner docs.
2. Copy Branded docs URL. It ends in /partner-docs/r/ followed by your reseller's short name.
3. Give it to your merchants' developers instead of P2P's own docs. The content is the same; only the look is yours.

Your own web address

Owner

P2P can run your portal, your merchants' portal and their customers' payment page under your own domain, for example app.yourbrand.com with api.yourbrand.com behind it. There is no page for this in your portal: P2P sets it up, and only where P2P has switched custom domains on. Ask P2P platform support whether it is available to you before you promise it to a merchant.

How it goes, once P2P agrees:

1. You choose the two addresses. Both must be under one domain you own.
2. P2P registers them and gives you the DNS records to add: one that proves you own the domain, and the ones that point both addresses at P2P.
3. You add those records at your domain provider.
4. P2P checks them, switches your domain on, and the security certificate is issued for you.

From then on, people who open your address see your colours and icon from the sign-in page onwards; the sign-in page still shows the P2P name and P2P's support contact. P2P's own admin pages are never served on your domain. P2P remains the operator, and the one responsible for your merchants' customers' data, whichever address they use.

When something goes wrong with branding

Your logo or colours don't show where you expect

Owner

What you see. A merchant's portal or payment page shows P2P's look, or colours that are not yours. Or saving says Enter a valid hex colour (#RRGGBB)., Failed to save colours. or Failed to upload logo.

Why it happens. The merchant has colours of its own set by P2P, which win over yours. Or the merchant is no longer in your book. Or the page is a sign-in page on P2P's address, which carries P2P's look. Or the colour is not a six-digit hex code, or the logo is the wrong type or too large.

What to do

1. Check the merchant is still in Merchants. If it is not, ask P2P.
2. Re-enter each colour as # and six digits or letters A–F, and press Save colours.
3. Upload the logo as JPEG, PNG or WEBP, 5 MB or smaller.
4. If one merchant shows other colours, ask P2P platform support whether it has its own set, and to remove them if it should show yours.
5. For sign-in pages in your colours, ask about your own web address. The P2P name and P2P's support contact stay on them.

Who to ask. P2P platform support.

You want your own web address

Owner

What you see. Your merchants and their customers see P2P's address, and you want them to see yours. There is no setting for it in your portal.

Why it happens. Custom domains are set up by P2P, not in the portal, and only where P2P has switched the feature on.

What to do

1. Ask P2P platform support whether custom domains are available for you.
2. Follow Your own web address: choose the two addresses, add the DNS records P2P gives you, and wait for P2P to switch it on.
3. Only then tell your merchants the new address.

Who to ask. P2P platform support.

A rail is a way for money to reach someone: a bank account, a payment gateway, or the service that reads a slip's QR code. Your merchants normally use their own. You can add yours underneath them.

Rails at a glance

Your rail	What it does for your merchants	Live?
Slip providers	Checks slips for every merchant in your book that has no key of its own.	Yes, from the moment you save a key.
Payment gateway	Takes QR deposits when a merchant's own accounts and gateway cannot.	Only where P2P has switched routing through resellers on.
Bank accounts	Takes bank-transfer deposits when a merchant's own accounts and gateway cannot.	Only where P2P has switched routing through resellers on.

All three need P2P's merchant creation switch. Whether routing through resellers is on is decided by P2P per environment and is not shown in your portal: ask P2P platform support before you rely on it, or before you tell a merchant your accounts will catch its deposits.

The order a deposit tries is explained in Whose money you might hold.

Your slip-checking key

Owner

Bring your own slip-verification provider key. Every merchant assigned to you inherits it — a merchant with its own key keeps that, otherwise it falls back to yours, then to the platform default.

1. Open Slip providers.
2. Under Add a provider key, choose the Provider, enter the API key from your provider, and a Base URL (optional) only if the provider told you to. Press Save key. Saving replaces your current active key.
3. On the key's row, press Test. Paste the QR payload from a real slip (the text its QR code holds), optionally the Expected amount (THB, optional), and press Run test. Paste the QR payload from a real slip to probe this provider. Nothing is saved.
4. Connection OK — slip verified means it works. Provider returned an error means the key, the address or your account with the provider needs fixing.
5. Activate and Deactivate switch a key. With no active key, your merchants fall back to the platform default provider.

When a slip cannot be checked, it is not lost: it waits for a person in the merchant's slip review.

Your payment gateway

Owner

Bring your own payment gateway. When a merchant's own rail is exhausted, every merchant assigned to you inherits it — merchant → reseller → platform. (Takes effect only where the reseller gateway tier is enabled.)

1. Open Payment gateway.
2. Under Register your gateway, enter the API key and API secret from your provider, and optionally a Label (optional) and Base URL (optional). Press Save gateway. Saving replaces your current active gateway.
3. Press Test on its row. It asks the provider for your balance and changes nothing.
4. Activate or Deactivate. With no active gateway, your merchants fall through to the platform rail.
5. The provider must know where to report payments. This page does not show that address. Ask P2P platform support for it and paste it into your provider's settings. Until then, deposits through your gateway sit unfinished.

To give one merchant its own gateway instead, use that merchant's Gateway tab (The merchant's payment gateway).

Your bank accounts

Owner

Add your own bank account(s) to receive P2P transfers. When a merchant assigned to you runs out of its own accounts, the deposit falls to yours — merchant → reseller → platform. (Takes effect only where the reseller tier is enabled.)

1. Open Bank accounts. Under Add a bank account, choose the Bank and enter the Account holder name and Account number. Press Add account. By adding it you vouch for this account — it can receive deposits immediately.
2. On a row: Edit to correct the bank, holder or number, and Activate or Deactivate. Inactive accounts are skipped by the deposit cascade.
3. To switch several at once, tick them (or Select all accounts) and press Activate selected or Deactivate selected.
4. If you see … account(s) are active but still cannot receive deposits: They are not verified, so the deposit cascade skips them. Verification is what makes an active account routable. Accounts you add yourself are verified as you add them; ask P2P platform support to verify the others.

A customer's money that lands in one of these accounts belongs to the merchant, and you pay it on (Settlement).

Deposit accounts: order, limits and money held

Owner

Deposit accounts shows the same accounts as Bank accounts, in a different order and with different controls. Ordered by priority — the cascade's first tiebreak. Accounts at the same priority are picked by the allocation plan below, and one at the depositor's own bank goes last. To add or switch accounts, use Add, activate or deactivate accounts.

1. Allocation plan: Round robin, Least accumulated first or Random. It is saved as soon as you choose.
2. One account: press Edit to set its Daily limit (THB) (blank for Unlimited) and its Priority, then Save. The account is skipped once it receives this much in a day (Asia/Bangkok).
3. What it received: Today's deposits, Last used, and View transactions for the deposits themselves.
4. Finding one: search by holder, last 4 digits, status or bank, or tick Unroutable only.

Money held, and money you moved out

Each account shows Money held: in − out (recorded) = remaining. Out (recorded) = payments recorded from this account + money moved out. Withdrawal payouts are not counted, because the account they were paid from is not recorded.

When cash has left an account for any reason other than paying a merchant (moving it to another account of yours, for example):

1. On the account, press Record money moved out.
2. Fill in Amount moved out, Date (the date on your bank statement), What was it for?, and Sent to if it went to an account.
3. Press Record it.

Lowers …'s remaining. It doesn't change what you owe anyone. To pay someone, use Record payment. No screen can undo it, so check the amount first. If the button says Reactivate this account before settling it., switch the account on first.

Gateway reconciliation

Owner

This page does not need the merchant creation switch. It matters only when deposits go through your gateway.

Deposits credited on our side but not confirmed 'success' at the gateway (manual-slip fallback). Check each with the provider, then confirm or flag. Tracking only — this moves no money.

1. Open Gateway reconcile. Leave Pending only ticked to see what still needs checking.
2. On a deposit, press Evidence. What the gateway was told and What the slip says sit side by side; a value that disagrees is marked doesn't match or not the gateway account.
3. Check the payment with the gateway provider, using Gateway txn and the bank reference.
4. Press Confirm if the provider has it, or Flag, write what is wrong, and press Save flag.
5. Customer attachments: Slips a customer or your staff attached for reconciliation. These are not verified and do not prove payment — forward one to the payment gateway's support channel when you need them to check a transfer.

Recording a reconciliation moves no money; the deposit stays credited and settle-able.

Screenshot to comeThe Gateway reconcile page with one deposit's evidence open

When something goes wrong with your rails

A bank account or gateway of yours never receives deposits

Owner

What you see. On Deposit accounts, an account shows Today's deposits at ฿0 and Last used Never. Or your gateway is active but no deposit ever uses it. Or you see … active account(s) will not receive deposits

Why it happens. Your rails come after your merchants' own, and only in some cases:

• Routing through resellers may not be switched on where you work. P2P decides this.
• While a merchant's own accounts or gateway can take a deposit, the deposit goes there.
• Only merchants currently in your book can use your rails.
• A deposit is matched to a withdrawing customer first whenever that is possible.
• The account is switched off, not verified, has reached its daily limit, or loses to accounts with a higher priority.

What to do

1. Ask P2P platform support whether routing through resellers is switched on for you.
2. Check the account is Active. Tick Unroutable only: any account listed needs verifying by P2P.
3. Check its Daily limit and Priority against your other accounts.
4. Remember it is a fallback: a quiet account can simply mean your merchants' own rails are coping.

Who to ask. P2P platform support.

Gateway reconcile lists deposits you don't recognise

Owner

What you see. Gateway reconcile lists deposits whose Gateway status is not a success, with Confirm and Flag.

Why it happens. Your gateway never confirmed these payments, so each deposit was credited to the customer from the slip they uploaded. The customer already has the money in P2P. What is not yet known is whether it really reached your gateway account.

What to do

1. Open Evidence and compare the two sides.
2. Ask your gateway provider about the payment, quoting Gateway txn and the bank reference. Forward an attachment to their support if they need the picture.
3. Confirm if they have it.
4. If they do not, Flag with what you found, and tell P2P platform support and the merchant: a customer may have been credited for money that never arrived.

Who to ask. Your gateway provider, then P2P platform support.

Deposit accounts shows money held that has already left

Owner

What you see. An account's Remaining is higher than what is in the bank.

Why it happens. Out (recorded) counts only what someone recorded in P2P: payments to merchants recorded from that account, and money you recorded as moved out. Cash moved without being recorded is not counted.

What to do

1. If you paid a merchant from it but have not recorded that yet, record the payment, choosing this account in Paid from if the form offers it.
2. For any other money that left, use Record money moved out (Money held).
3. If it says Reactivate this account before settling it., switch the account on first.

Who to ask. P2P platform support, to undo a mistaken record. No screen offers an undo.

Slips stop being checked after you change your key

Owner

What you see. Merchants say their customers' slips now wait in review, or stay "verifying" for a long time, since you saved a new key. Test says Provider returned an error

Why it happens. Saving a key replaces your active key for every merchant that uses yours. If the key, the address or your account with the provider is wrong, slips cannot be checked automatically and wait for a person instead.

What to do

1. On Slip providers, run Test with a real slip's QR payload.
2. If it fails, save the correct key, or press Deactivate so your merchants fall back to P2P's default.
3. Tell your merchants to clear the slips waiting in their slip review (see the merchant manual's A slip has been "verifying" for a long time).

Who to ask. Your slip-checking provider, then P2P platform support.

Each entry starts with what you see on screen, explains why in plain words, then gives the steps. Read the "Don't" box before you press anything. Every entry ends with who to ask.

Find your situation

If you see…	Go to
You can't get past the 6-digit code, or your temporary password has expired	I can't get in
A page, menu or button this manual describes isn't in your portal	A menu or button is missing
A staff login named "… Platform Support" that nobody created	A "Platform Support" login
A merchant says a customer's deposit or withdrawal is stuck	A merchant reports a stuck transaction
A new merchant shows SUSPENDED, or can't take payments	A new merchant can't take payments
A merchant lost its API key or HMAC secret	Lost credentials
A merchant's top-up is waiting, or its usage credit is below zero	Top-ups and overdraft
A branch's withdrawals are refused, or never matched	Withdraw allowance
Someone has left, or a merchant's owner is locked out	Someone has left
Rate is below the platform floor.	Rate refused
Branches stopped matching other merchants' customers	Pool switched off
This share would exceed the remaining reseller spread for this merchant.	The share would exceed your spread
Reseller gross is ฿0 for a merchant with volume	You earn nothing on a merchant
An agent has left, or you no longer pay them	An agent has stopped working with you
A merchant asks for the money that landed in your account	A merchant says you are holding its money
A merchant disputed your payment, or you recorded one wrongly	A settlement payment is wrong
A pool member's notice, or a Settlement cell marked "Soon"	Pool notices and "Soon"
The fee ledger has not been opened yet, so nothing is being billed. This is not a zero balance. or the Money page doesn't match your invoices	The Money page doesn't match
A fee payment on Money you don't recognise	A fee payment you don't recognise
Your logo or colours don't show on a merchant's pages	Branding doesn't show
You want your own web address	Your own web address
One of your bank accounts or your gateway never receives deposits	Your rail never receives
Gateway reconcile lists deposits	Gateway reconcile
Remaining is higher than your bank balance	Money held that has left
Slips wait in review after you changed your slip-checking key	Slips stop being checked

Access and support

I can't get in

Owner Viewer

What you see. After your email and password, the code page refuses your code. Or you have a new phone and no authenticator. Or first sign-in says Your temporary password has expired. Ask your administrator for a new invite. Or the page says Too many sign-in attempts. Try again in a few minutes.

Why it happens. A temporary password works for 24 hours. The 6-digit code must come from the authenticator you set up for this login, on a phone whose clock is right. The code page mentions backup codes, but the reseller portal does not issue any, so a lost phone always means a reset. Too many failed tries lock sign-in for a few minutes.

What to do

1. Check your phone's time is set automatically, wait for a fresh code, and try once more.
2. If that fails, or the phone is lost, or the temporary password expired, ask for a reset:
   • a co-owner: another owner resets you on Staff → Reset credentials;
   • the founding owner: contact P2P platform support;
   • an agent: an owner resets you on MDR users → Reset password.
3. Sign in with the new temporary password within 24 hours, and set up your authenticator again (Your first sign-in).
4. If nobody at your reseller can sign in, contact P2P platform support. A reseller account that P2P has suspended locks out every login.

Who to ask. An owner of your reseller; P2P platform support for the founding owner.

A page, menu or button this manual describes isn't in your portal

Owner Viewer

What you see. There is no Create merchant button, no Slip providers or Payment gateway, no Manage Bank Account group, or no Gateway or Staff tab on a merchant. Or a page says You are not permitted to create merchants. Ask an administrator to enable this for your reseller. Or, as an agent, most of the menu is missing, and the report says This report covers the whole reseller — the fee waterfall and every MDR's share — so it is available to owners and staff only.

Why it happens. Two things decide what you see: your role, shown at the bottom of the menu, and P2P's merchant creation switch for your reseller. With the switch off, the pages that create and equip merchants, and everything about your own bank accounts, are not shown. An agent's login is read-only by design.

What to do

1. Check your role at the bottom of the menu, and compare it with Your role in five minutes.
2. If you are an owner and need a missing page, ask P2P platform support for the merchant creation switch.
3. If you are an agent, see the MDR manual: the pages you have are the ones meant for you.
4. If Money shows money you hold for merchants but you have no Settlement page, tell P2P platform support. You need it to record paying that money on.

Who to ask. P2P platform support.

A "Platform Support" login we never created

Owner

What you see. Staff lists a staff login whose name ends in "Platform Support" and whose email ends in "@impersonation.invalid". Nobody on your team added it.

Why it happens. When P2P platform support opens your portal to help you, the session runs through this login. Nobody can sign in to it: it has no password and no authenticator. In your portal the session is read-only, so it cannot change anything. P2P's own records name the real person, and when.

What to do

1. Note the date you first saw it.
2. Ask P2P platform support for the record of the support session.
3. If nobody at P2P opened one, report it to P2P as a security concern.

Who to ask. P2P platform support.

A merchant reports a stuck deposit or withdrawal

Owner

What you see. A merchant calls: a customer says they paid and nothing was credited, a slip has been "verifying" for hours, or a withdrawal was never paid. Your portal shows only totals, not single deposits or withdrawals.

Why it happens. Individual transactions live in the merchant portal. Almost every fix is made there, by the merchant's own staff, or by P2P for the few things only P2P can decide.

What to do

1. Ask the merchant for the details in Who to contact: the deposit or withdrawal ID or merchant order ID, the amount and time, and the slip.
2. Open the merchant's page → Act as merchant → Read-only — see what their staff see, change nothing (Act as a merchant). Find the transaction under Transactions and open it.
3. Match what you see to the merchant manual's When a deposit goes wrong or When a withdrawal goes wrong, and send the merchant's staff to that entry. Most fixes, such as approving or rejecting a slip or closing a withdrawal before paying it, need their own login.
4. Use Support write — also unstick transactions (fulfil a withdrawal, request a cancel, retry a webhook) only when the merchant cannot act and the fix is on its short list: filing a cancellation request for a stuck deposit, retrying a webhook, or recording a withdrawal payment the merchant has already made from its bank.
5. For anything only P2P can do, such as crediting a split deposit or deciding a cancellation request, send the merchant to P2P platform support with the details from step 1.

Who to ask. The merchant's own staff first; P2P platform support for what only P2P can do.

Fees and pools

A rate is refused as "below the platform floor"

Owner

What you see. Creating a merchant, a rate turns red and Create merchant stays greyed out. Or Set fee says Rate is below the platform floor. Or a bulk fee says Rate is below the platform floor.

Why it happens. You may not charge a merchant less than the platform base P2P gives you, for that fee type. A bulk fee is all or nothing, so one refusal means no merchant was changed.

What to do

1. On the create form, read your base on the line under the rate, and enter at least that.
2. Elsewhere, enter a rate at or above your base and save again.
3. If you believe your base is wrong, ask P2P platform support. Only P2P can change it.

Who to ask. P2P platform support.

Branches stopped matching across merchants after a pool change

Owner

What you see. Branches that used to match other merchants' customers now wait longer. Their Matching pool shows Isolated, or the pool shows Disabled on Matching pools.

Why it happens. A disabled pool reaches nobody: its members keep their membership but match only their own customers. A new pool starts disabled. A branch that was taken out of a pool is isolated until it joins another.

What to do

1. Open Matching pools. If the pool is off and it is safe to switch it back on, press Enable and confirm. Matching resumes from the next round.
2. For one branch, check its Matching pool and admit it again if it should be in (A branch's matching pool).

Who to ask. P2P platform support, for a pool you do not own.

The names of businesses and people below follow P2P's glossary, so the same thing has the same name in the portal, in this manual and in the merchant and branch manuals. Where a term has its own section, it links there.

Terms

• Act as merchant: opening a merchant's portal as that merchant, read-only or in support write, to see what its staff see. More
• Agent: this manual's everyday word for an MDR partner. More
• Allocation plan: how deposits are shared across your bank accounts: round robin, least accumulated first, or at random. More
• Branch: this manual's everyday word for a sub-merchant. More
• Buy-in: money a branch pays to a pool's owner before it may join a pool that requires one. It becomes the branch's withdraw allowance. More
• Co-owner: a login you add on Staff. The portal calls it staff; it has the same rights as the founding owner. More
• Custody: merchants' money that landed in your bank accounts or gateway, which you hold for them. More
• Direct: on Settlement, a merchant's own business, as opposed to one of its branches. More
• Dispute: a merchant telling you a payment you recorded did not arrive or is wrong; the amount goes straight back to what you owe. More
• Fee type: Pay-in (on deposits) or Pay-out (on some branch withdrawals). Each has its own rate, base and shares. More
• Founding owner: the owner login P2P created with your account. Only P2P can reset or switch it off. More
• Gateway reconciliation: checking, with your gateway provider, deposits that were credited from a slip because the gateway never confirmed them. More
• Group: a set of your merchants, for pricing them together or giving an agent a share on all of them. More
• Hosted checkout: the P2P payment page your merchants send their customers to. It shows your brand. More
• MDR partner: a sales agent who earns a share of your merchants' volume, and signs in with a read-only login. More
• MDR share: an agent's percentage of a merchant's volume, for one fee type, paid out of your spread and capped by it. More
• Matching pool: a group of branches, possibly of different merchants, whose customers can be matched with each other. More
• Merchant creation switch: P2P's setting that lets your reseller create merchants and use your own slip-checking key, gateway, bank accounts and Settlement. More
• Money held: for one bank account, money in minus money recorded as out equals what remains. More
• Platform base: P2P's own rate for each fee type, and the lowest rate you may charge a merchant. More
• Pool notice: a pool member telling you it paid back, sent a buy-in, or wants its buy-in back. Nothing changes until you confirm it. More
• Rail: a way for money to reach someone: a bank account, a payment gateway, or the slip-checking service. More
• Rate: what a merchant pays you, as a percentage of its volume, for one fee type. More
• Record payment: telling P2P, after you have transferred it, that you paid a merchant money you held for it. It moves no money. More
• Reseller: a business that brings merchants to P2P, prices them and supports them; in this manual, you.
• Slip-checking key: your account with a slip-checking provider, used for every merchant in your book that has none of its own. More
• Spread: a merchant's rate minus your platform base: your commission, before agents' shares. More
• Sub-merchant: a part of a merchant with its own customers and staff; in this manual, a branch.
• Support session: someone opening a portal as another party, with every action recorded. More
• Usage credit: a merchant's prepaid balance with P2P, which goes down as its deposits settle. More
• Void: withdrawing a payment you recorded by mistake, before the merchant disputes it. More
• Volume: the money in a merchant's settled deposits (pay-in), or in its branches' withdrawals filled from outside the branch (pay-out). Fees and agents' shares are worked out on it. More
• Withdraw allowance: a branch's balance that lets its withdrawals be filled with other people's money. It is always checked for a fill from another merchant. More
• Withdraw-allowance limit: the per-merchant setting for whether the allowance is also checked on fills from the same merchant. More