Ductor
Start
C

Checkout.com

Checkout.com connector for Ductor — available as both a trigger and a destination.

Payment
1
Actions
0
Triggers

Example

A complete route that uses Checkout.com — an input is matched, scored by a strategy, assigned, and dispatched to Checkout.com.

type == "order" && status == "paid"key →TriggerNew OrderWebhookAssignleast_loadedStrategyfulfillmentassignedcheckout_comActionDelivered
▸ Show the code
// Fulfill an order the moment payment clears.
engine.Route(ductor.Route{
    Match:    `routable.type == "order" && attrs.status == "paid"`,
    Strategy: "least_loaded",
    Pool:     "fulfillment",
    Then: ductor.Workflow{
        Mode: ductor.Async,
        Steps: ductor.Steps{
            ductor.Connector("checkout_com", "run"),
        },
    },
})
 
// Durable, observable, exactly-once.
decision, err := engine.Dispatch(ctx, routable)

What you can build

Fulfill on payment

Trigger fulfillment the moment a charge succeeds.

Dunning workflow

On a failed charge, retry and escalate through the right path.

Revenue alerts

Route large or anomalous transactions for review.

Authentication

OAuth2 client credentialsNo auth

Credentials are stored AEAD-encrypted at rest — usable by the engine, never readable back.

Actions

No actions on this connector.