> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getruba.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Move Billing to Another Provider
> Transfer customer identities and saved payment methods without exposing card data
export const RubaSocials = () => {
if (typeof document === "undefined") {
return null;
}
const inject = () => {
const footer = document.getElementById("footer");
if (!footer || document.getElementById("ruba-socials")) {
return false;
}
const isDark = document.querySelector("html.dark") || document.querySelector('html[class*="dark"]');
const lineColor = isDark ? "#383838" : "#e8e8ed";
const iconColor = isDark ? "#8e8e93" : "#86868b";
const markColor = isDark ? "#ffffff" : "#08080c";
const hoverColor = "#0071e3";
const div = document.createElement("div");
div.id = "ruba-socials";
div.style.cssText = `display:flex;align-items:center;gap:20px;padding-top:20px;margin-top:20px;border-top:1px solid ${lineColor};width:100%`;
const logo = `Ruba`;
const spacer = ``;
const ig = ``;
const li = ``;
const x = ``;
const github = ``;
div.innerHTML = logo + spacer + ig + li + x + github;
footer.appendChild(div);
return true;
};
if (!document.documentElement.dataset.rubaSocialsObserver) {
document.documentElement.dataset.rubaSocialsObserver = "true";
const observer = new MutationObserver(() => {
if (!document.getElementById("ruba-socials")) {
inject();
}
});
observer.observe(document.body, {
childList: true,
subtree: true
});
}
setTimeout(() => {
if (!inject()) {
const interval = setInterval(() => {
if (inject()) {
clearInterval(interval);
}
}, 500);
setTimeout(() => clearInterval(interval), 10000);
}
}, 300);
return null;
};
Leaving Ruba is a coordinated migration, not a card-data export. Payment methods are vaulted with Stripe under Ruba's Merchant of Record setup, so Ruba and the destination processor move them directly under payment-network and PCI rules.
Start by emailing [support@getruba.com](mailto:support@getruba.com) with the destination account. The process is support-assisted rather than self-serve.
## Migration boundary
| Asset | Transfer behavior |
| ----------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Customer identity and billing details | Transferred |
| Saved payment methods | Transferred directly to Stripe or through secure PAN export to another PCI-compliant processor |
| Products, prices, discounts, and benefits | Recreate at the destination |
| Active subscriptions | Recreate at the destination, align renewal dates, then cancel in Ruba |
Stripe-to-Stripe is the shortest path. A different processor must be able to receive Stripe's secure PAN export. Raw card details never pass through you, and customers should not need to enter them again.
## Sequence the cutover
Create and verify the account that will receive billing. Send its details to Ruba support so the organization can enter offboarding.
Ruba coordinates a processor-to-processor transfer. This step preserves PCI boundaries and does not provide raw card data to your team.
Recreate products, prices, discounts, and benefits using the destination provider's tools or API. Ruba does not produce a customized configuration export.
Set the first destination charge to the existing subscription's next Ruba renewal date. After the destination subscription is active, cancel its Ruba counterpart.
When the 120-day reserve period has ended, withdraw the released amount to the connected bank account.
## What offboarding changes
Existing subscriptions continue to renew until you cancel them, but new checkouts are disabled. Payouts pause for 120 days after the final Ruba transaction. The reserve covers refunds and disputes that can arrive after the original payment; any remaining amount is released after that window.
Do not leave matching subscriptions active at both providers. That can charge the customer twice. It also creates later Ruba transactions, which delays the start of the 120-day reserve window.
## Timing and edge cases
A migration to your own Stripe account can usually finish within a few business days. Other processors often require several weeks of coordination.
No. Customer and saved-payment-method migration has no Ruba fee.
Yes, provided the processor is PCI-compliant and can receive the secure PAN export.
Refunds and disputes for Ruba-processed payments continue to be handled against the reserved balance. A remainder below the normal country payout threshold can be resolved with support.
Historical orders, invoices, and reports remain available during offboarding. Transaction records are retained for compliance for at least five years after processing.
The transfer is intended to avoid that. Their most visible change should be the new billing descriptor after the destination begins charging them.