Independent crypto payment research desk
CoinPayments Legacy and V2 migration notes
For teams trying to understand migration work before changing checkout infrastructure.
Referral disclosure: marked outbound CTA may use a sponsored referral URL. This does not make the site official.
Referral: open checkout account path01
Inventory what exists
List every plugin, API key, webhook endpoint, checkout page, cron job, finance report, and support macro that references the old integration.
02
Stage the change
Use a test environment, replay historical edge cases, confirm webhook idempotency, and keep a rollback plan that does not require customer action.
03
Communicate carefully
Avoid telling customers to enter wallet secrets anywhere. A migration notice should explain checkout changes without requesting private keys, seed phrases, or passwords.