Merchant Agreement
Operational responsibilities for businesses connecting websites and payment accounts to NextPay.
Effective August 4, 2026Authorization
The merchant confirms that it controls the registered website, webhook endpoint and configured bank or mobile-money accounts, and is authorized to receive payments through them.
Integration responsibilities
The merchant must install current NextPay gateway and webhook files, protect credentials, use HTTPS, keep the allowed domain accurate and test invoice crediting before production use. API-key or webhook-secret rotation requires immediate integration updates.
Customer instructions
The merchant is responsible for accurate account names, account numbers, QR codes and payment instructions. The merchant must provide customer support for incorrect amounts, wrong recipients, reversals and manual-review cases.
Verification and duplicates
NextPay matches receipt reference, recipient, amount, date and invoice note where supported. A transaction reference may be credited only once. Uncertain webhook outcomes may require manual investigation before any retry.
Subscriptions and suspension
The merchant must maintain an active subscription. NextPay may suspend checkout access for expiration, abuse, security risk, false account information, unlawful activity or material breach of this agreement.
Data and notices
The merchant must provide any customer notices and lawful basis required for processing checkout and receipt information. Telegram chat IDs must belong to recipients authorized to receive payment notifications.
Support and records
The merchant should retain its own invoices, account statements and business records. NextPay logs support verification and troubleshooting but are not a replacement for official bank or tax records.
Contact
Questions may be sent to surafel1231@gmail.com or Telegram @surafelnardos.