লাইভ করা

প্রোডাকশন ইন্টিগ্রেশনের চেকলিস্ট: সিক্রেট, টাইমআউট, অবজারভেবিলিটি, ব্যর্থতার মহড়া ও সাপোর্ট।

Version v1 · updated 2026-02-01

An integration is not done when it works; it is done when it fails safely. This is the list we check before an app is listed in the marketplace, and it is the same list we would apply to our own services.

Before you ship#

  1. Secrets live in a manager, not in env files committed to a repository, and are rotatable without a deploy.
  2. Every outbound call has a timeout. A call with no timeout is an outage waiting for a slow dependency.
  3. Retries use full jitter and a cap, and only on idempotent operations or with an idempotency key.
  4. Webhook handlers acknowledge fast and process asynchronously, deduplicating on event_id.
  5. You log request_id, status and code — and never customer PII.
  6. You have an alert on error rate and on webhook delivery failure, not just on uptime.
  7. You have tried it: pull the network, expire the token, return a 500 from your own handler, and watch what the merchant sees.

Deprecation policy#

ChangeNoticeWhere announced
New endpoint or fieldNone (additive)Changelog
Behaviour change30 daysChangelog + email to app owners
Breaking change90 days + new versionChangelog, email, response header
Emergency security fixAs fast as safety allowsStatus page + email

A deprecated endpoint answers with a `sunset` header carrying the retirement date long before it stops answering at all. Nothing disappears without a date you can see in a response.