Part 10 - Merchant Account Setup for B2C and B2B Payments
Learn how one merchant account can support B2C checkout and B2B invoices, payment links, settlement, refunds, and provider setup.
Merchant Account Setup for B2C and B2B Payments
Before a business accepts payments, it needs a merchant setup: a verified business identity, a payment provider account, a settlement bank account, supported currencies, and enabled payment methods.
For MugMori, the simplest model is one business with one Stripe or HitPay merchant account. That same account can support immediate B2C checkout and a different B2B invoice or payment-link workflow.
What is a merchant account?
A merchant account is the provider relationship that allows a business to accept payments and receive settlement funds. It is not the same as a customer account, a bank login, or a database of card numbers.
| Setup item | Purpose |
|---|---|
| Business identity | Shows who is legally responsible for the sale |
| Business verification | Helps the provider assess eligibility and risk |
| Settlement bank account | Receives the provider payout |
| Country and currency | Determines availability, pricing, and settlement rules |
| Payment methods | Controls how customers can pay |
| Refund and dispute policy | Defines how the business handles payment problems |
| Provider account reference | Connects the business records to Stripe or HitPay |
The provider owns payment processing and settlement. The merchant remains responsible for the product, customer relationship, fulfilment, refunds, and business records.
One merchant account for B2C and B2B
For one MugMori legal business, use one merchant account unless there is a clear reason to separate accounts.
MugMori business
|
v
One Stripe or HitPay merchant account
|
+--> B2C checkout: card, PayNow, wallet
|
+--> B2B workflow: invoice, payment link, bank transfer, card
The account can have different customer journeys without creating separate payment identities.
| Area | B2C | B2B |
|---|---|---|
| Buyer | Individual customer | Company or organisation |
| Payment timing | Usually immediate | Immediate, invoice, or agreed credit terms |
| Common methods | Cards, PayNow, wallets | Invoice, payment link, bank transfer, card |
| Checkout data | Name, email, delivery address | Company name, billing address, purchase order |
| Pricing | Retail price and promotions | Quote, bulk price, or contract price |
| Support | Individual order support | Account, invoice, and procurement support |
| Settlement owner | MugMori business | MugMori business |
B2C merchant setup
A B2C setup should make immediate payment easy and clear:
- Verify the MugMori business with the provider.
- Connect the business settlement bank account.
- Enable the required currencies.
- Activate cards and selected Singapore payment methods.
- Publish customer-facing refund and delivery policies.
- Test successful, failed, refunded, and cancelled payments.
- Confirm that provider webhooks update the order correctly.
The customer pays MugMori, not the payment provider as the seller. Stripe or HitPay processes the transaction and later settles funds to the merchant.
B2B merchant setup
B2B usually uses the same merchant account but adds business information and a slower payment workflow.
| B2B requirement | Why it matters |
|---|---|
| Company legal name | Identifies the buyer on the invoice |
| Billing address | Supports invoicing and tax records |
| Business registration or tax number | May be required for business documentation |
| Purchase order number | Links the payment to the buyer's procurement process |
| Payment terms | Defines when the invoice is due |
| Contact person | Gives the seller an accountable business contact |
| Delivery and billing addresses | Separates fulfilment from accounting information |
For a small MugMori business, begin with payment-before-fulfilment using an invoice or payment link. Offer credit terms such as Net 30 only after the business has a clear approval, credit-limit, and collections process.
Merchant setup with Stripe or HitPay
| Setup question | Stripe | HitPay |
|---|---|---|
| Can one business support B2C and B2B? | Yes, subject to account capabilities | Yes, subject to account capabilities |
| Common B2C flow | Checkout or Payment Element | Hosted checkout, payment link, or API request |
| Common B2B flow | Invoice, payment link, or card payment | Invoice, payment link, or card/PayNow payment |
| Who owns the merchant relationship? | The verified business | The verified business |
| Where are credentials kept? | Server-side secret configuration | Server-side secret configuration |
| Where do funds settle? | Configured merchant payout account | Configured merchant payout account |
Exact features, eligibility, currencies, fees, and settlement timing depend on the provider account and current terms. The provider dashboard is the source of truth.
What belongs in the merchant database?
The application may store merchant business metadata and provider references:
| Field | Example | Safe to store? |
|---|---|---|
| Business name | MugMori Pte. Ltd. | Yes |
| Country and currency | Singapore, SGD | Yes |
| Provider | Stripe or HitPay | Yes |
| Provider account reference | acct_provider_reference |
Yes, if non-secret |
| Enabled methods | Cards, PayNow | Yes |
| Account status | Pending, active, restricted | Yes |
| Secret API key | sk_live_... |
No; use environment secrets |
| Card number or CVV | Customer card data | No; use hosted or provider components |
| Bank login credentials | Online banking credentials | No |
For a single merchant, this table may initially be represented by application settings. A database model becomes more useful when the business supports multiple providers, currencies, legal entities, or marketplace sellers.
When separate merchant accounts are justified
Create separate merchant accounts only when the business reason is clear:
| Situation | Why separate accounts may help |
|---|---|
| Separate legal companies | Each entity has its own responsibility and settlement |
| Different countries | Local verification, currencies, and payout rules may differ |
| Separate brands | Reporting and customer statements need clear separation |
| Marketplace sellers | Each seller may need its own connected or merchant account |
| Different risk profiles | The provider may require separate underwriting |
| Independent accounting | Revenue, refunds, and payouts must not be mixed |
Multiple merchant accounts add onboarding, reconciliation, reporting, refund, and support complexity. They should not be created merely because the same business serves both consumers and companies.
Safe payment boundaries
The merchant setup does not change the security boundary:
- React Native or another frontend starts a checkout request.
- Django or FastAPI calculates trusted order totals.
- The backend uses provider secrets to create the payment or invoice.
- Stripe or HitPay hosts or processes sensitive payment details.
- Webhooks confirm payment state.
- The merchant database stores order state and safe provider references.
The recommended MugMori starting point is one verified merchant account, separate B2C and B2B customer workflows, and one consistent order and payment record owned by the business.