You can move your products and billing to another provider, but the migration must respect who owns
each record. OurPay stores your organization, catalog, customers, orders, subscriptions, and ledger.
Payment credentials created through the central PayPal account belong to that receiving merchant
account and are not a merchant-downloadable export.
Do not promise that PayPal wallet tokens can be transferred. Unless PayPal and the destination
provider approve a provider-to-provider migration for the exact accounts involved, customers must
authorize a new payment method with the destination merchant.
What can be exported or recreated
Migration sequence
Inventory the active business
Export customers, active subscriptions, next billing dates, products, prices, discounts, open
refunds, open disputes, and the seller-payable ledger. Keep stable mappings between OurPay IDs
and destination IDs.
Configure the destination
Create the destination merchant account, catalog, tax configuration, webhooks, fulfillment, and
customer portal. Test both success and failure paths before moving a real customer.
Collect new payment authorization
Ask each affected customer to approve a payment method with the destination merchant unless an
account-to-account token migration has been explicitly approved. Never request or handle raw
PayPal credentials yourself.
Recreate subscriptions
Schedule the first destination charge for the customer’s next unbilled period. Preserve the
product, quantity, currency, discount, trial state, tax treatment, and renewal date where the
destination supports them.
Stop OurPay renewals
After the replacement subscription and authorization are confirmed, cancel the matching OurPay
subscription before its next charge. Verify the status in both systems to avoid double billing.
Reconcile the old processor account
Keep the central PayPal integration available for refunds, reversals, and disputes on historical
captures. Reconcile those outcomes against the final seller payable.
Avoid double billing
The safest migration unit is one customer subscription at a time:
- Record the OurPay subscription ID and next renewal date.
- Create the destination customer and subscription without charging an already-paid period.
- Obtain payment authorization for the destination merchant.
- Confirm the destination’s first billing date.
- Cancel the OurPay renewal and verify the resulting status.
Do not run bulk cancellation before the destination catalog, authorization flow, and webhook
processing are proven. Do not leave both systems scheduled to charge the same period.
Refunds and disputes after migration
A destination provider cannot normally refund a capture created by the central OurPay PayPal
account. Continue handling those refunds and disputes in OurPay so the original PayPal capture,
order, tax record, and seller ledger remain linked.
Keep the old webhook configuration active until every refundable transaction and dispute window
you are responsible for has ended. The actual duration comes from your contracts, provider rules,
and applicable law; OurPay does not publish a universal migration holding period.
Final seller settlement
Payouts are disabled by default. Migrating away does not itself create
a withdrawal or reduce Seller Payable. If the gated PayPal Payouts rail is enabled, use its normal
audited payout lifecycle; otherwise the deployment operator must reconcile any final external
settlement separately, including later refunds or lost disputes.
Get help
Contact support@ourpay.com before disabling an organization that has
active subscriptions, open refunds or disputes, or an outstanding seller payable. Include the
organization ID and destination provider, but never email API secrets, PayPal credentials, PANs, or
bank account numbers. 
