Merchant onboarding looks like a paperwork exercise until the first settlement fails. Then it becomes clear that onboarding is where the operating model is decided: who can approve a refund, which party holds the card data, how a duplicate payment is reversed, and who reconciles the gateway report against the bank statement.
This checklist is written for a Bangladeshi business joining a payment aggregator, and for platforms that onboard many merchants. It covers commercial terms, compliance evidence, technical integration, operations and the tests that should pass before volume is switched on. Each item names an owner and the evidence that proves it is done.
1. Commercial and legal
- Signed merchant agreement and fee schedule. Owner: Finance. Evidence: executed agreement that states the percentage fee, any fixed fee, settlement cycle and who bears chargeback costs.
- Refund and chargeback policy. Owner: Finance and customer service. Evidence: written policy with approval limits and the evidence pack required for a dispute.
- Reserve or hold terms. Owner: Finance. Evidence: clause explaining whether the provider may hold a rolling reserve and for how long.
- Settlement account in the business name. Owner: Finance. Evidence: bank account letter matched to the trade licence and tax documents.
- Pricing for exceptions. Owner: Finance. Evidence: written treatment of failed payouts, manual reversals and currency conversion.
2. Compliance and KYC
- Trade licence, TIN and VAT or BIN registration. Owner: Finance. Evidence: current copies with expiry dates tracked.
- Company documents and board resolution. Owner: Legal. Evidence: incorporation certificate, memorandum, and a resolution naming the signatories.
- Beneficial ownership declaration. Owner: Compliance. Evidence: KYC forms for owners above the provider's threshold.
- PCI DSS scope statement. Owner: Engineering. Evidence: a data-flow diagram showing whether card data is hosted by the provider, redirected, or handled by your systems.
- Privacy notice and processing terms. Owner: Legal. Evidence: customer-facing notice that names the payment provider as a processor or independent controller.
- Sanctions and prohibited-business screening. Owner: Compliance. Evidence: screening result and the policy for high-risk categories.
PCI scope is often misunderstood. If your checkout redirects to the provider, your scope is smaller than if you post card fields from your own page. The answer changes your evidence obligations, so write it down before integration starts.
Re-verification matters as much as initial approval. Set a review date for licences, ownership changes and bank account changes, and treat a change of settlement account as a risk event rather than an administrative update. Sector directives, such as Bangladesh Bank's 17-point cybersecurity directive for financial institutions, can add requirements when you operate in or serve a regulated sector.
3. Technical integration
- Sandbox credentials and test accounts. Owner: Engineering. Evidence: a shared, documented test environment that does not use production keys.
- Authentication and secret storage. Owner: Engineering. Evidence: keys stored in a secrets manager, not in code or spreadsheets, with an owner and rotation date.
- Idempotency keys on payment creation. Owner: Engineering. Evidence: a repeated request returns the same transaction instead of charging twice.
- Signed webhooks with replay protection. Owner: Engineering. Evidence: signature verification, timestamp tolerance and a dead-letter queue for failed events.
- Timeout and retry behaviour. Owner: Engineering. Evidence: documented rule for when to retry, when to query status, and when to show an error to the customer.
- Amount, currency and rounding rules. Owner: Engineering and Finance. Evidence: test cases for discounts, partial payments and refunds that do not create one-taka mismatches.
- Payment method matrix. Owner: Product. Evidence: which methods appear on web, mobile app and counter, and what happens when one is unavailable.
4. Operations and support
- Refund authority limits. Owner: Customer service. Evidence: role-based permissions and an approval log.
- Dispute evidence pack. Owner: Finance. Evidence: a template containing order, delivery, communication and refund records.
- Daily reconciliation routine. Owner: Finance. Evidence: gateway report, bank statement and ledger compared, with an exception queue.
- Exception ownership and service level. Owner: Operations. Evidence: named person for failed payments, late settlements and unmatched refunds.
- Provider contact matrix. Owner: Operations. Evidence: named contacts for technical, settlement and fraud issues, plus an escalation path.
- Customer messaging for pending payments. Owner: Customer service. Evidence: approved wording for pending, failed and reversed transactions.
5. Go-live verification
Run this test matrix in sandbox and again with a small live transaction before scaling:
- Successful payment with correct order status and receipt.
- Declined payment with no order created and a clear customer message.
- Timeout where the customer is charged but your system does not receive a response.
- Duplicate submit from a double click or a retried request.
- Full refund, partial refund and refund of a settled transaction.
- Webhook replay and an out-of-order event.
- Settlement report matched to the bank credit, including fees.
- Chargeback notification routed to the dispute owner.
- Provider outage path: can you disable the method without taking down checkout?
- Access review: who can issue refunds, export reports and change keys?
Common mistakes
- Starting integration before the PCI scope is written down.
- Using production keys in a staging environment.
- Treating the webhook as the only source of truth.
- Giving every support agent refund permission.
- Reconciling only at month-end, when the exception queue has already grown.
- Leaving the settlement account in a personal or group name.
- Forgetting that refunds and chargebacks change the reconciliation, not just the order.
Where this fits in our work
If you are integrating a payment aggregator or cleaning up an existing one, start with Commerce Systems. The pricing page explains how we scope the work. For the control that keeps onboarding honest after go-live, read the daily payment reconciliation guide.
Sources
- PCI Security Standards Council, accessed 17 November 2026.
- bKash Developer Portal, accessed 17 November 2026.
- SSLCommerz Developer Documentation, accessed 17 November 2026.
- Bangladesh Bank, Mobile Financial Services data, accessed 17 November 2026.
- The Daily Star, "BB issues 17-point cybersecurity directive amid rising threats", accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.