Meridian Payments Terms of Use
Rules for using the website, sandbox, dashboard, API, and Meridian Payments services.
1. Document status
These Terms govern access to the website, sandbox, dashboard, API, and other Meridian Payments components. Commercial payments, pricing, limits, settlement, and payouts are governed by a separate merchant agreement.
2. Accounts and companies
- provide accurate information and keep it current;
- grant access only to authorized company representatives;
- never share credentials with third parties;
- report suspected compromise and terminate unknown sessions;
- provide documents reasonably required to review a company or project.
3. Sandbox and integration
The sandbox is for testing and creates no real monetary obligation. Test statuses, credentials, rates, and balances are demonstrative. API keys belong to a project, are shown once, and must be treated as secrets.
4. Payments and status
A payment is confirmed only after a valid provider event is received and processed. Interfaces may show intermediate states. Idempotency is required for write requests, and merchants are responsible for unique keys and correct webhook handling.
5. Fees, FX, and T+N
Fees, FX markup, limits, and T+N rules are set in project configuration and the merchant agreement. T+N changes affect future payments only. Withdrawals are available solely from released balance after all applicable holds and checks.
6. Refunds and payouts
Full and partial refunds cannot exceed the original payment. A payout request reserves available balance and may be paused or rejected for insufficient funds, invalid destination, fraud risk, sanctions, or legal requirements.
7. Prohibited use
- illegal goods, services, or transactions;
- fraud, money laundering, prohibited financing, or sanctions evasion;
- unauthorized access, vulnerability scanning, or disruption;
- key sharing, webhook forgery, or access to another tenant;
- use that infringes third-party rights.
8. Suspension
Meridian may restrict a company, project, key, or operation to protect security, respond to a breach, comply with law, or prevent harm. Where permitted, the user receives the reason and remediation path.
9. Intellectual property and liability
The interface, brand, documentation, and software are protected by applicable law. Access transfers no ownership rights. Warranties, availability commitments, and liability limits are defined in the commercial agreement.
10. Changes and contact
The current version is published here. Material changes are communicated in advance where required by contract or law. Questions may be submitted through the website contact form.
The Meridian team will respond through the contact form.