Go-Live Gates
The gates a merchant must clear before Cresora takes it live, and how to read them.
A provisioned merchant rests at ACTIVE (probe and test transactions only). Before
Cresora moves it to LIVE — the state that processes real payments — its go-live
gate must pass.
The gate items
Read them at Partner Portal → Onboarding → Go-live gate, or via
GET /api/v1/merchants/{merchantId}/go-live-gate. The evaluation covers:
| Item | What it verifies |
|---|---|
GATEWAY_MERCHANT | The merchant's gateway account is provisioned |
PROCESSOR_PROFILE | A processing profile is boarded at the processor |
HIPAA_BAA | The signed BAA is on file (healthcare merchants) |
PCI_SAQ | The completed PCI SAQ is on file |
UNDERWRITING_PROVIDER_VERIFIED | Underwriting verification completed |
CP_DEVICE_HEARTBEAT | Card-present only: the device has a live heartbeat |
CP_PIM_TEST_TXN | Card-present only: a test transaction succeeded on the device |
Each item reads as passed / pending / blocked, with the failing items named — the same list the API returns.
Going live is an action, not an automatism
When every applicable item passes, Cresora performs the go-live — it is an explicit
review action, not an automatic flip. The merchant moves ACTIVE → LIVE and the
merchant.live webhook fires. (merchant.activated is the earlier, provisioning
event — a merchant that is ACTIVE is not yet accepting real payments; see the
state reference →.)
When a gate blocks
The gate names the failing item. Compliance items resolve through the portal's Compliance pages (upload the BAA / SAQ); gateway and processor items are Cresora-side provisioning — if one sits blocked, raise it with your account manager with the merchant id and the item name.