Coverage: what is actually available to you?
Confirm the countries, currencies, methods, business jurisdictions and industries available for your merchant profile. A country name on a website is not a guarantee of onboarding or method access.
Separate local collections from payouts. Ask for the actual payment journey, beneficiary requirements and method-specific limitations, then document what is in scope for the first launch.
If your customers pay in MYR, review Malaysia online banking and QR payments and list the banks or QR apps they need. Bring your expected payment volume and order-matching requirements to the integration discussion.
Orders: how does your application avoid ambiguity?
- How are merchant references represented, and which identifiers must your team store?
- What happens if an order request times out and is retried?
- Which order states are pending, final or eligible for review?
- What are the amount and currency formats, limits and instruction expiry rules?
- How should duplicate or out-of-order updates be handled?
These are evaluation questions, not a claim that every provider implements the same controls. Follow the current API reference for your approved environment.
Notifications: which source determines payment outcome?
Agree the documented authentication and verification process for requests and notifications. Ask about retries, acknowledgements, delayed delivery and the supported procedure for checking an order's status.
Do not fulfil an order based only on a customer browser redirect or a screenshot. Define the documented confirmation signal and the reconciliation process with your payment provider.
Operations: what happens outside the happy path?
Review expired instructions, delayed payments, rejected payouts and mismatched references with the support team. Confirm what information is safe and necessary to include in an investigation.
- Named support channel and escalation responsibilities.
- Reconciliation records and matching process.
- Funding, settlement timing and treatment of non-working days where applicable.
- Fees, transaction limits and any method-specific operating conditions.
Production: what must be verified before launch?
Get current endpoint documentation from the provider, confirm how credentials are issued and stored, and agree a test plan. Include interruptions and exceptions as well as successful transactions.
PAYJN's current service focus is API-based local pay-in and payouts. Credit card acquiring and USDT payment acceptance are not part of this service. Review our integration approach and discuss the requirements for your first market.