Merchant FAQ

Get concise answers to common merchant operations questions with links to the right detailed workflow pages.

#When is my merchant account ready for production traffic?

Production readiness requires approved account verification, settlement setup, event monitoring, and successful controlled test flows.

#What should I do when a payment link expires before customer completion?

Issue a new link tied to the same merchant order reference and keep fulfillment blocked until confirmed payment state is received.

#How should we handle invoice reminders and cancellations?

Use a defined reminder cadence, then expire or cancel by policy so finance and customer support records remain consistent.

#What happens when a subscription renewal fails?

The renewal should follow your configured retry and dunning policy, then pause or cancel after retry exhaustion.

#How do we investigate payout exceptions?

Compare settlement batch totals against internal ledger records, isolate affected payouts, and escalate unresolved destination or network exceptions.

#What evidence is required for dispute response?

Provide payment references, fulfillment proof, customer communication history, and policy context before response deadlines.

#Which metrics should we watch daily?

Track authorization success, confirmation delay, refund/dispute velocity, payout exception rate, and unresolved reconciliation variance.

#When should merchant operations escalate to engineering?

Escalate immediately for persistent state mismatches, repeated event delivery failures, or controls that prevent safe customer-impacting actions.

Last updated: 2026-08-04

Compatibility window: Applies to the currently shipped Ryvra docs portal and interfaces published through August 2026.