Payment anxiety peaks when the UI stalls after redirect, or when your bank shows a charge but Rhinobird balance stays flat. Most cases split into three buckets: payment never completed, payment completed but crediting delayed, or payment completed under the wrong account. This guide walks verification steps that protect you from duplicate pay, then escalation paths the Membership Services Agreement and Credit Top-Up Agreement recognize.
Confirm whether payment actually succeeded
Rhinobird treats payment success when the provider callback or internal system records confirmation—not when you merely click pay. Wait for an in-app success state. If the browser closed early, sign in with Login / Sign up and check membership center, Credit balance, and order history before attempting a second checkout.
Check your bank or wallet app for pending versus settled charges. Pending authorizations can disappear; settled duplicates need support.
Verify the credited account
Top-ups especially require the correct account before payment (Credit Top-Up Agreement). Teams with multiple logins often pay on account A while watching balance on account B. Confirm email or user id on the checkout screen matches the account that owns History.
Unpaid or cancelled orders
You may cancel unpaid membership orders through order management; they never activate Subscription Credits. If checkout failed outright, no Order Snapshot performance should exist—safe to retry once you confirm no settlement occurred.
Delayed crediting
Some channels batch confirmations during maintenance or regional latency. If success UI appeared but balance lags minutes, refresh account views. If lag exceeds a reasonable window (hours), gather order id, payment timestamp, and provider receipt screenshot, then contact support.
Escalation package for support
- Rhinobird account identifier (email or phone used for Login / Sign up)
- Order number or merchant reference from checkout if shown
- Payment channel name as displayed on the payment page
- Amount, currency, date/time (timezone noted)
- Screenshot of bank/wallet settlement (mask PAN/security codes)
- Whether purchase was membership (Pricing) or Credit top-up
Reach the customer service portal, telephone 13378452864, or email support@rhinobird.ai. The Membership Services Agreement lists failure to issue benefits and platform-attributable inability to use services among issues the operator verifies within a reasonable period.
Avoid making it worse
Do not immediately pay again on repeated clicks—duplicate charges are a common outcome. Do not file card chargebacks while crediting is still processing unless your bank requires it; chargebacks on top-ups oblige you to return granted Credit and may restrict services (Credit Top-Up Agreement). Do not use unofficial top-up resellers promising instant Credit.
After crediting resolves
Confirm Subscription Credits or top-up balance, read expiry rules on purchase or top-up pages, and run a test Generate. Archive the Order Snapshot or receipt for finance.
Related policies
Service Agreement, Privacy Policy (payment data), About Us. Duplicate charge specifics: duplicate-or-mistaken-charges article in this category.
Keep a simple log for finance: date, account email, order id, payment channel label from the checkout screen, and whether the purchase was membership from Pricing or an official Credit top-up. That log speeds support review and prevents your team from opening three tickets for the same incident.
Failed payment and missing credit feel identical in the moment—separate them with order records, one account, one verified charge, then support with proof.