From your first project to daily reconciliation.
Practical Meridian guides for preparing a project, taking your first payment and everyday reconciliation.
Prepare your project for onboarding
Define the project before integration. Clear boundaries reduce follow-up questions and help establish the right setup.
- Prepare a working website or application URL, service description, customer countries and expected volume. Explain how the team can review a private product.
- Submit your Telegram contact, website, business category and verification type. Choose “Discuss with our team” when unsure.
- Agree on methods, fees, release times and payouts before integrating. Terms for one project may not apply to another.
- Sign in after approval. Check the project name and settlement schedule. Contact support before proceeding if they differ from the agreed setup.
- Open API & Webhooks and select the integration management control. Create a clearly named key and store its one-time secret in secure server storage.
A key belongs to its project. Never expose it in browser code, screenshots, public repositories or messages.
Complete your first test payment
Test how your order receives confirmation, not just how the success screen looks.
- Confirm with the team that the project is in test mode and understand its limits before sending requests.
- Create an order with a unique orderId. The current API accepts amountKopecks as a string: 235000 means RUB 2,350. Use the supported SBP or CARD method.
- Send the project credential in X-Api-Key and a separate Idempotency-Key for the operation. Reuse that idempotency key when retrying the same request after a network failure.
- Complete the hosted test form. Test success, failure and expiry separately. Do not use real payment credentials to simulate transactions.
- Match the order to the payment on your server. A success-page redirect is not payment confirmation: check the API status or a verified signed event.
A successful test validates your integration, not live acquiring availability. Production activation is agreed separately.
Reconcile operations with confidence
Payment status, turnover and available funds are different measures. Check each for its intended purpose.
- Select the workspace period and verify the project. Compare matching periods and currencies in your system and Meridian.
- Start with successful operation count and turnover, then review fees and refunds to explain the difference from order totals.
- Find a disputed operation using its ID or order reference. Record its status and the check time before retrying or contacting support.
- Configure an HTTPS address in API & Webhooks. Store the signing secret on your server and verify every notification.
- Process repeated notifications without delivering a service twice. Query the payment API for its current state when events are insufficient for reconciliation.
Send the project ID, payment ID and expected outcome to support. Never include passwords, secrets or full card details.
Check available funds before a payout
A successful payment is not automatically a withdrawable balance. Your project’s settlement schedule determines availability.
- Review pending, available and reserved funds separately. Do not treat their combined total as immediately withdrawable.
- Open the holds view to inspect upcoming releases. T+N applies to new payments; changing the rule does not rewrite existing history.
- Use the agreed network and a verified address for USDT payouts. The current API uses allowlisted TRC20 addresses.
- Check the amount and available funds. A request reserves funds: a delayed response is not a reason to repeat it with a new idempotency key.
- Discuss recipient lists, schedules and operation submission with the team before bulk contractor settlements. The current workspace has no batch-file upload or automatic scheduling controls.
An accepted request does not mean a completed transfer. Check the final status and follow the agreed reconciliation process.
Start with your project.
Tell us what you sell and where you operate. We will follow up with questions and an onboarding proposal.
support@meridian-pay.io