Troubleshooting
Typical MeerPartners problems and how to solve them: a click or conversion was not credited, postback rejected, payout not arriving, a private offer is not visible, slug taken, balance at zero.
A collection of typical situations with step-by-step solutions. If your problem is not on the list — check the Errors reference or contact support.
A click or conversion was not credited
The click went through but is not in the statistics — or a conversion happened but there is no commission.
Check whether it is a bot
Traffic from bots and crawlers is excluded from attribution. Assess the quality of the traffic source — incentivized and low-quality traffic is more often not credited.
Check the attribution window
A click is valid for a limited time (30 days by default). If the user bought later — the click is outside the window, and the conversion becomes unattributed. See Attribution.
Make sure the business returns click_id
The cookie is often lost (Telegram, WebView, mobile). The most reliable way is for the business to pass aff_click from its landing page back into the postback. This removes the dependency on the cookie.
Check that the event matches the model
A CPL offer should receive a lead event, a CPA/RevShare offer — sale. If the event does not match the model, the conversion is recorded, but the commission is not accrued.
A conversion is not lost silently
Even without attribution, a conversion is recorded with the unattributed status and goes into deferred resolution. If the click arrives with a delay, the platform re-binds the conversion to the influencer.
Postback rejected
The business server sends a postback, but the platform returns an error.
Check the signature (HMAC)
The signature is computed over the string {METHOD}\n{PATH}\n{X-Timestamp}\n{SHA256(body)} with the API key secret. A mismatch → a signature error. Compare the algorithm and the request body byte by byte.
Check the timestamp (anti-replay)
X-Timestamp must be within ±300 seconds of the current server time. Clock drift on your server → the postback is rejected as stale. Synchronize the time (NTP).
Check ref and external_order_id
ref is the click_id or the link code; without a correct ref, attribution will not find the click. external_order_id is mandatory — it is the idempotency and deduplication key.
Check the scope and ownership of the key
The API key must have the postback scope and belong to the same tenant as the offer. The X-Api-Key-Id and X-Tenant-Id headers must match the key.
Resending is safe
The postback is idempotent by external_order_id: resending the same order returns {duplicate:true} and does not create a duplicate. Retrying the postback is fine. Exact codes — API error codes.
Payout not arriving
The request is created, but the money does not come.
Look at the request status
requested — created; processing — with the provider; paid — paid out; failed — declined (money returned to the balance); on_hold — under a manual anti-fraud check.
Clarify the payout method
Telegram Stars and bank/manual are processed by an operator manually — this is slower than the automatic card and USDT. Check that the details are correct (for USDT — the network strictly TRC-20).
Check the anti-fraud hold
Before a payout, a manual check is possible (account freshness, volume spike, matching details). A request in on_hold is awaiting review.
There will be no double payout
If a payout is stuck due to a network timeout, the platform itself clarifies the outcome with the provider and finalizes the request. Do not create a duplicate manually — the system uses an idempotency key. More details — Payout methods.
A private offer is not visible
The offer exists, but it is not in the influencer catalog.
Check access to the private offer
Private offers are visible only to invited publishers. If there was no invitation — the offer will not appear in the catalog.
Check the invitation status
The invitation may have expired (INVITE_EXPIRED), been revoked (INVITE_REVOKED) or exhausted its usage limit (INVITE_EXHAUSTED). Request a new one from the business.
Check whether the offer is paused
An offer that is paused or under moderation is hidden from the catalog. Wait for it to be activated.
Error creating a business: slug taken
When registering a business, the system reports that the address (slug) is already in use.
TENANT_SLUG_TAKEN
A business slug must be unique within the platform. If it is taken — choose another. Pick a variant that does not exist yet: add a suffix, a region or shorten the name.
Come up with a unique slug
Use Latin letters, digits and a hyphen. Avoid overly generic words — they are taken more often.
Retry the creation
Enter a new slug and save. On a repeat error, try another variant.
Balance at zero, accruals stopped (for the business)
Conversions keep coming, but commissions are not accrued, and the offer is paused.
The deposit ran out
If the escrow balance does not have enough funds for the next conversion, the offer is automatically paused (OFFER_AUTO_PAUSED_NO_FUNDS), and the conversion moves to pending_funds — it is not lost.
Top up the escrow balance
Go to Balance and top-up and add funds. A top-up below the minimum returns DEPOSIT_BELOW_MIN.
Wait for auto-resume
After a top-up, the accumulated pending_funds conversions are automatically promoted to regular accruals, and the offer resumes. The action is idempotent.
Do not let it hit zero
Watch the remaining balance so the offer does not pause in the middle of traffic. Auto-top-up is marked "soon" in the interface and is not available yet — top up in advance manually.