Skip to main content
Ruba resells approved digital goods and services as Merchant of Record. Reviews verify the seller, confirm the product follows the Acceptable Use Policy, and keep fraud, refund, and dispute exposure within safe limits.

Before the first payout

Complete the real sales path before submitting. Review is faster when Ruba can see configured products and benefits, a working website, checkout, API credentials, webhooks, and automatic fulfillment. Then open Finance → Account and complete all three gates:
  1. Describe the business, products, and intended Ruba use.
  2. Complete Stripe Identity KYC with an accepted identity document and selfie.
  3. Connect a payout account through Stripe Connect Express.
The first review may take up to 14 days depending on queue volume, weekends, and holidays.

What changes during a later review

Ruba reviews organizations asynchronously at sales thresholds and continuously monitors transactions. Most checks require no action. Checkout and renewals continue. A requested payout displays Held until approval, then proceeds automatically. Reviewers compare the current business with the originally approved use case and examine recent refund, dispute, and risk signals.

Operating standards

Answer customer issues

You remain responsible for product support. When Ruba includes you in a customer case, reply within 48 hours. Ruba may refund the affected customer and warn the organization after no response; repeated failures can lead to offboarding.

Use sandbox for tests

Never test with real card details. Processors can classify repeated artificial purchases as card testing. Use sandbox, or use a free product or 100% discount when a production path must be checked without moving money.

Control chargebacks

Ruba’s operating threshold is 0.4%, below the roughly 0.7% level at which card networks may begin monitoring and penalties. A buyer can dispute a transaction for up to 120 days. When risk rises, Ruba first works with you to reduce it. Escalation can then move through individual refunds, payout holds through the chargeback window, pausing new payments, and finally blocking the account and refunding customers. Early network signals may trigger an automatic refund and related subscription cancellation for lower-value transactions before a chargeback is formally filed.

Stay inside policy

An Acceptable Use Policy breach stops payment processing and holds payouts for review. Suspected intentional fraud can result in immediate blocking. Otherwise, Ruba normally requests a response within 48 hours and may make a test purchase to verify the customer journey. Transactions and subscriptions that violate policy may need to be refunded and canceled.

Evidence and administration

Growth thresholds and changing risk signals can trigger more than one review. This is part of ongoing payment-platform risk management.
They help verify identity, online presence, and the nature of the product. The information is internal, is not displayed publicly, and is used for review and risk assessment.
A 100% discount code lets the team verify the journey from unpaid user to automated fulfillment. If that is not practical, provide a recording that clearly shows the same complete transition.
Invite the new administrator under Settings → Members, have them complete identity verification under Finance → Account, ensure no payout is pending, then email support from the current administrator address confirming the transfer.