Destination Status

Every host on your PCI Proxy destination allowlist has a status that controls whether the forward proxy may send card data to it. A destination is created in the ENABLED state and can be toggled without losing its configuration or audit history. Only ENABLED destinations are reachable — a request to a DISABLED (or removed) host is rejected with 403 DESTINATION_NOT_ALLOWED.

Workflow

A destination can be removed from either state — enabled or disabled. Removal is permanent; the record leaves the allowlist, though the deletion stays in the append-only audit log.

Status	Description
`ENABLED`	The destination is active. The forward proxy may send card data to this host. A destination starts here on registration.
`DISABLED`	The destination is suspended. Its record and audit history are kept, but the forward proxy will not use it until it is re-enabled. Requests to it return `403 DESTINATION_NOT_ALLOWED`.
(removed)	The destination has been deleted from the allowlist. It is no longer returned by List and requests to it are rejected. The deletion remains in the append-only audit log.

Getting Started

Reference

Customers

Network Tokens

Customer Sessions (Enrollment)

Checkout Sessions

Payment Methods (Checkout)

Checkout Builder

Payment Methods (Direct Workflow)

PCI Proxy

Payments

Pre-Debit Notifications

3DS2 Setup

Unreferenced Refunds

Dry-run

Payment Links

Recipients for Marketplace

Sellers (Franchise)

Subscriptions Plans

Subscriptions

Payouts

Organizations

Reports

Installments

AI Caller

Communications Campaigns

Conversion Rate

Banking Connectivity

Webhooks

Destination Status

Workflow

Destination status

​Workflow

​Destination status

Workflow

Destination status