Source type

Checkout.com Source Configuration

Checkout.com sources receive payment, dispute, payout, and account webhooks with Checkout.com signature verification.

CHECKOUT_COMPOST, PUT, PATCH, DELETESecret KeyPayments
Checkout.com webhook verification documentationAll source types
Checkout.com sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.Checkout.comProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLCHECKOUT_COMProvider credentialsignatureVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.

Checkout.com configuration

Create a Checkout.com source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Secret Key values for provider signature. FastHook uses these settings to validate each Checkout.com delivery before it enters the routing workflow.

Source Type

CHECKOUT_COM

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Secret Key

Checkout.com source config
{
  "type": "CHECKOUT_COM",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "CHECKOUT_COM",
      "webhook_signing_secret": "secret-key"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Checkout.com request contract

FastHook computes HMAC-SHA256 hex over the raw request body with the configured secret key and compares it with cko-signature.

POSTPUTPATCHDELETE

Checkout.com headers

Preserve cko-signature when sending Checkout.com test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

cko-signature

Checkout.com webhook signature generated with the secret key.

Checkout.com setup

  1. Configure the Checkout.com webhook endpoint with the generated FastHook Source URL.
  2. Copy the Checkout.com secret key into FastHook.
  3. Route by event type such as payment_approved, payment_declined, or dispute events.

Continue with Checkout.com