Source type

Checkout.com Source

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.
FastHook keeps the provider-facing contract on the source. Accepted requests are stored before routing, while rejected requests keep enough evidence to debug signature, method, and challenge failures.

When to use this source type

Choose the CHECKOUT_COM source type when Checkout.com is the system sending webhook requests into FastHook. The source type keeps sender-specific setup close to the source: accepted methods, verification headers, challenge handling, and the exact credential fields are documented together so operators do not need to translate a generic HMAC form into a provider-specific contract.

FastHook verifies the source before accepted traffic is queued. A valid request is stored with verified: true, then connections route it to destinations. A bad signature, wrong token, or missing provider header is rejected as SOURCE_AUTH_FAILED. A method outside the allowed set is rejected as SOURCE_METHOD_NOT_ALLOWED.

FastHook configuration

In the dashboard, create a source, set Source Type to Checkout.com, keep Authenticate enabled when verification is required, and fill the fields below.

Source Type

CHECKOUT_COM

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Secret Key

Copy this value from Checkout.com and store it on the FastHook source.

{
  "type": "CHECKOUT_COM",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "CHECKOUT_COM"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

HTTP methods

This source accepts only the methods listed below. Keep the set narrow so provider mistakes and accidental test calls are visible as rejected requests instead of being silently accepted.

POSTPUTPATCHDELETE

Headers and verification

FastHook verifies the provider-specific values below before the request is accepted. The comparison is done against the raw inbound request body or the exact provider-specific signing input described here.

cko-signature

Checkout.com webhook signature generated with the secret key.

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

Provider setup checklist

  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.
  4. Open Checkout.com webhook verification documentation when you need the provider's event list, dashboard steps, or retry policy.

Troubleshooting

  • No request appears: the provider is not calling the generated FastHook Source URL, the source URL was copied before saving, or the provider has not completed its setup validation.
  • 405 method rejected: the provider sent a method outside POST, PUT, PATCH, DELETE. Edit the source only if the provider documentation says that method is expected.
  • 401 source auth failed: check the configured FastHook field, the provider signing secret, and the header names listed on this page.
  • Signature mismatch: make sure the provider signs the same public Source URL it calls and that no proxy, parser, or manual resend changed the raw request body before FastHook received it.

Related docs