Not a PSP · One-time purchase · Your Stripe + Square accounts

One dashboard for every Stripe & Square account.
Save cards. Rebill anywhere. Cloak the metadata.

Rellum is the all-in-one platform we built so you can accept payments and run recurring billing across all your Stripe and Square accounts from one place. Not a payment processor. You keep your own accounts. Buy once. Run it yourself.

Cards · Apple Pay · Google Pay · Shopify orders · Token vault · Cross-account rebills · Radar-safe rebills · Rotation + failover · Metadata cloaking

One-time sale not a monthly PSP cut

Your accounts Stripe + Square stay yours

White-site metadata Stripe sees the site you opened the account with

Exactly What We Provide

Everything in one platform. No guesswork.

This is the full product — accept, vault, rebill, rotate, recover, and cloak. Built for operators who need Stripe and Square to keep working while sales come from any storefront.

✓

Accept cards, Apple Pay, Google Pay & Shopify orders

Take checkout from your stores, wallets, and Shopify. All payments land in the same operations dashboard.

✓

Securely save customer payment methods

Vault cards and tokens server-side. Charge again with one click — no customer has to re-enter the card.

✓

Cross-account rebilling system

Save a card once, then rebill that same customer on a different Stripe account — or rotate across many. The vault is not locked to one merchant.

✓

Radar-safe rebilling — rebills pass Stripe Radar smoothly

When we rebill, Rellum shapes the charge so Stripe Radar treats it like a normal returning customer — not a sudden off-session blast. Rebills go through smoothly instead of dying on Radar blocks.

✓

Automate recurring charges

Run scheduled and batch rebills from the vault. Set amounts, pick accounts, or let rotation choose the next healthy account.

✓

Payment rotation + automatic failover

Spread volume across multiple Stripe and Square accounts. If one goes down, the next account takes the charge automatically.

✓

Recover failed payments with smart retries

Declines retry on the next account in rotation. Failed-payment view, reason codes, and retry from the same dashboard.

✓

Real-time revenue & transactions

See every charge, account, customer, amount, status, and risk score live. Export CSV / JSON anytime.

✓

Edit Stripe payment metadata

Custom details appear directly in your Stripe Dashboard. Put the white website — the site you opened Stripe with — so Stripe sees that site, not the store that made the sale.

Rebilling Engine

Save the card once. Rebill it on any Stripe account.

This is the core of Rellum. Customers are vaulted with their payment methods. You can charge that token against Account A today and Account B tomorrow — without asking the customer again.

How rebilling works

Customer pays once — card is saved in the Token Vault
You pick any connected Stripe (or Square) account
One-click charge or full batch rebill of the vault
Rotation engine can auto-pick the next healthy account
Radar-safe path so Stripe Radar treats the rebill as a returning customer
If the charge fails, smart retry moves it to the next account
Full log: who was billed, on which account, amount, status

Why this matters

If you only rebill on the same Stripe account that captured the card, one restriction kills your recurring revenue.

With Rellum, the customer stays in your vault. The processing account is interchangeable. Subscriptions and rebills keep running while you rotate merchants.

Cross-account token portability

Stripe Radar

When we rebill, charges pass Stripe Radar smoothly.

Raw off-session rebills look like sudden, high-risk charges. Rellum shapes every rebill so Radar sees a normal returning customer — not a blast. That is how rebills go through instead of dying on Radar blocks.

        What Radar-safe rebilling does
        Attaches a consistent Radar session to the batch so Stripe sees one customer journey
Uses mandate + returning-customer signals Stripe expects on a legitimate rebill
Warms the charge with fresh fingerprint data before the PaymentIntent fires
Spaces batch rebills with human-like delay and jitter — not a firehose
Sends the white-site origin and metadata so the charge matches the account identity

        Rebills pass Radar smoothly
      

Why rebills fail without this

Stripe Radar scores off-session charges harder. A vaulted card hit from a new account, a new origin, or a tight loop of retries looks like card testing.

Rellum keeps the rebill inside the risk profile Stripe already trusts: same customer, expected cadence, clean website, no leaked sales-store Origin. Recurring revenue keeps posting.

Metadata Cloaking

Put the white website in Stripe. Work normally.

Sales can come from Store A. In Stripe metadata you send the website you opened the account with — the clean / white site. That URL is what appears in the Stripe Dashboard. Stripe does not see the storefront that actually made the sale.

What you set per account

Website URL — the white site you used to open Stripe
Statement descriptor — what the customer sees on their bank statement
Store / origin — what Stripe request logs attribute the charge to
Custom metadata — extra fields you want visible in the Dashboard

Use the same website you verified the Stripe account with. Keep processing as a normal business on that identity.

What Stripe Dashboard shows

metadata.website_url = https://your-white-site.com

metadata.origin_domain = your-white-site.com

statement_descriptor = WHITESTORE

sale storefront = not sent

Cloaking profiles can apply a full identity in one click (descriptor + URL + store name + metadata). Or set every field yourself.

Full Platform

Stripe + Square. Vault. Rotation. Analytics. One app.

All of this ships in the same dashboard. You are not stitching five tools together.

💳

Checkout you already use

Cards, Apple Pay, Google Pay, and Shopify orders. WooCommerce / Origin Bridge checkout if you want Store A to sell while processing stays on the clean account.

🗄

Customer + card vault

Name, email, country, source, risk level, last4, brand, expiry. Multiple tokens per customer. Export the vault. Search and filter instantly.

Save cards

🔄

Rebill any account

Single charge or batch engine. Choose the target Stripe/Square account or Auto (rotation). Recurring billing without locking LTV to one MID.

Recurring

🛡

Radar-safe rebills

When rebilling, Rellum passes Stripe Radar smoothly. Session tracking, mandate signals, fingerprint warmup, and human-paced retries keep recurring charges from looking like fraud.

Pass Radar

⚖

Rotation & failover

Equal, weighted, or priority routing. Per-account volume and order caps. Auto-pause a sick account. Next account takes over automatically.

Stay online

🛟

Failed-payment recovery

Dedicated failed view, reason codes, smart retries with delay/jitter, and fallback rules (retry next / pause / stop).

Recover revenue

👁

Live revenue dashboard

Real-time totals, success rate, volume by account, routing log, analytics charts, CSV/JSON export. See every dollar as it posts.

Visibility

🎭

Metadata + origin cloaking

White website in Stripe metadata. Server-side charge proxy so browser Origin does not leak the sales store. 8 vertical cloaking profiles included.

Keep accounts healthy

⬛

Stripe and Square together

Manage both processors in one platform. Rotate between Stripe accounts and Square — not two dashboards, not a third-party PSP taking a cut.

All-in-one

🔌

Store connections

Shopify, WooCommerce Origin Bridge, CSV import, and API. Pull customers in, vault cards, start rebilling the same day.

Onboarding

How It Works

Connect accounts. Vault cards. Charge anywhere.

Add Stripe & Square accounts

Paste keys, set the white website (the one you opened the account with), descriptor, limits, and optional proxy. Apply a cloaking profile if you want it done in one click.

Accept + save the card

Take the first payment from your store, Apple Pay, Google Pay, or Shopify. Rellum vaults the payment method for one-click and recurring use.

Rebill & rotate — Radar-safe

Charge that saved card on any connected account. Radar-safe shaping lets rebills pass Stripe Radar smoothly. Rotation, failover, and smart retries keep revenue moving if one account drops.

Who It's For

Operators who refuse to put all volume on one MID.

🛒 Stores + subscriptions

Sell on Shopify or Woo. Vault the card. Rebill later on a different Stripe account without breaking the subscription.

🏢 Multi-account teams

Many Stripe and Square accounts, one control plane. Rotate, cap volume, and fail over without spreadsheets.

🛡 Account-protection setups

Keep the white website in metadata so Stripe Dashboard matches the site the account was opened with. Sales site stays off the charge record.

Not a PSP

You own the accounts. You buy the software once.

Rellum is not a payment service provider. We do not take your money, hold reserves, or sit in the middle as the merchant. You process on your Stripe and Square. We give you the operating system.

Capability	A PSP / payfac	Raw Stripe or Square	Rellum
You keep your own Stripe & Square accounts	✕	✓	✓
One-time purchase (not a processing cut)	✕	N/A	✓
Save cards + one-click rebill	On their MID	Same account only	✓
Rebill the same card on a different Stripe account	✕	✕	✓
Rotate Stripe + Square with failover	✕	✕	✓
White-website metadata in Stripe Dashboard	✕	Manual	✓
Apple Pay / Google Pay / Shopify intake	Varies	✓	✓
Radar-safe rebills that pass Stripe Radar smoothly	✕	✕	✓
Smart retries on failed rebills	Basic	✕	✓
Live revenue + routing log	Their portal	Per account	✓
Self-hosted — keys stay on your server	✕	✓	✓

One dashboard for every Stripe & Square account.Save cards. Rebill anywhere. Cloak the metadata.