Current balance
See the amount that is eligible for payout now.
Ruba product infrastructure
Trace gross payment, tax, fees, refunds, disputes, balance, and payout in one ledger.
The number available for withdrawal is the end of a trace, not a black box. Every deduction remains attached to the transaction that caused it.
Live ledger engine
A completed order enters the ledger at gross value. Ruba then identifies tax held for remittance and all applicable platform or network costs before the seller balance changes.
See the amount that is eligible for payout now.
Follow orders, refunds, disputes, and related fees chronologically.
Choose when funds leave Ruba for the connected account.
Match every fee to the event that produced it.
Execution workflow
Connect the destination once, then move eligible funds when reconciliation is complete.
Complete the supported payout onboarding for the seller organization.
Orders settle into the seller ledger after tax and fees are identified.
Withdraw manually when the balance meets the provider’s currency threshold.
The payout becomes another ledger entry rather than disappearing from the history.
Capability matrix
Published Ruba pricing and provider pass-throughs remain separate in the record.
The transaction uses the rate attached to the seller’s current Ruba plan.
Any recurring-payment adjustment follows the seller’s applicable plan or legacy terms.
Card-network and processor pass-through for a non-US card.
The original transaction fee is not returned by the payment networks.
The actual dispute and related provider costs incurred for the case.
Applied when eligible seller funds are paid out.
Dashboard rows and API records describe the same finance activity, so an accounting workflow can import the ledger without scraping the UI. Customer currencies are converted for settlement while the original transaction context remains available for reconciliation.
Build with Ruba
Complete onboarding, review the ledger, and withdraw on your schedule.