Use this quickstart to understand the end-to-end RevBridge workflow.
Before restarting a full manual Stripe test pass, use the Fresh Stripe testing matrix in the reference docs. It lists supported migrations, expected blockers, rerun behavior, and audit checks.
Create a project
Open RevBridge and create a project for the acquisition migration. The project tracks Stripe keys, mapping state, dry-run output, execution status, and audit exports.
Project status starts as DRAFT and advances as required inputs are verified.
Add scoped Stripe keys
Add the seller and buyer Stripe keys requested by the app. Use scoped restricted keys, not root secret keys.
Both keys must be from the same Stripe mode, either test or live, and they must belong to different Stripe accounts. RevBridge rejects mixed test/live pairs and rejects using the same account as both source and destination.
After verification, RevBridge stores only the encrypted key material needed for the project and shows the last four characters for operator review.
Upload the customer mapping
Upload a CSV that maps seller customer IDs to buyer customer IDs.
old_customer_id,new_customer_id
cus_seller_123,cus_buyer_456
The CSV must contain Stripe cus_ identifiers in both columns. Rows without both values are skipped; malformed identifiers are rejected.
Saving new Stripe keys or uploading a new mapping clears any previous dry-run report. Run dry-run again after either change so execution uses the current source account, destination account, and customer map.
Run the dry-run
The dry-run validates subscription readiness without creating live buyer-side subscriptions.
It reports supported subscriptions, blockers, warnings, actions, price clone needs, and coupon clone needs.
Do not skip dry-run review
Execution should only happen after blockers are resolved and warnings are understood by the team responsible for billing continuity.
Execute and export audit records
After dry-run review and approval, queue the migration. RevBridge executes the approved actions with deterministic mutation keys and tracks completion progress. Payment processor gating is intentionally skipped for now while the provider decision is open.
When execution is finished, download the audit export as CSV or PDF and reconcile source subscriptions against buyer-side outcomes.