developer integration · coinpayments api
CoinPayments API planning guide
API integration work should be designed around states and failure handling, not only a happy-path invoice request. The notes below help teams write a safer implementation checklist.
$ verify coinpayments.world
status: independent guide
claim: not official
tracker: /index.php?event=pageview
safe rule: never share seed phrasesReferral disclosure: this button is a marked affiliate/referral link. Use it only after verifying the destination and deciding it fits your needs.
Referral button: continue carefullyModel invoice states
Track created, pending, confirming, paid, underpaid, overpaid, expired, refunded, and manual-review states where the provider supports them. Your order system should not collapse every incomplete payment into one generic error.
Validate callbacks
Treat callbacks as untrusted input until signature, source, amount, currency, and order reference are validated. Make handlers idempotent so retries do not duplicate fulfillment.
Design for network reality
Confirmation time varies by network and fee market. Build clear pending states and avoid shipping irreversible goods until your own threshold is satisfied.