Checkout.com MCP integration for AI agents.
Connect AI agents to Checkout.com through 4 structured actions, including get customer, create customer, and delete customer. Review authentication, inputs…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Checkout.com integration exposes
The Checkout.com Agent App exposes 4 provider-backed actions for finance work. Its current contract lets an authorized agent get a checkout.com customer and their linked payment instruments by id or email, create a checkout.com customer for storing reusable customer details, and delete a checkout.com customer and all linked payment instruments. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Checkout.com account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Checkout.com capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_customerREADGet a Checkout.com customer and their linked payment instruments by ID or email.
INPUTS: identifier
create_customerWRITECreate a Checkout.com customer for storing reusable customer details.
INPUTS: email / name / phone / metadata / default
delete_customerHIGH IMPACTDelete a Checkout.com customer and all linked payment instruments.
INPUTS: customer_id
update_customerWRITEUpdate stored details for a Checkout.com customer.
INPUTS: customer_id / email / name / phone / metadata
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer
identifierOPTIONAL- The Checkout.com customer ID or email address.
create_customer
emailREQUIRED- The customer's email address.
nameOPTIONAL- The customer's name.
phoneOPTIONAL- The customer's phone number.
metadataOPTIONAL- Customer metadata with up to 10 key-value pairs.
defaultOPTIONAL- The payment instrument ID to set as the customer's default instrument.
delete_customer
customer_idOPTIONAL- The Checkout.com customer ID.
update_customer
customer_idREQUIRED- The Checkout.com customer ID.
emailOPTIONAL- The customer's email address.
nameOPTIONAL- The customer's name.
phoneOPTIONAL- The customer's phone number.
metadataOPTIONAL- Customer metadata with up to 10 key-value pairs.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Customer
Get a Checkout.com customer and their linked payment instruments by ID or email. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_customerControl Create Customer
Create a Checkout.com customer for storing reusable customer details. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_customerVerify with Create Customer
Create a Checkout.com customer for storing reusable customer details. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_customerSAFETY BOUNDARY
Operate Checkout.com with explicit limits
- Authorize Checkout.com with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_customer` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Checkout.com rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Checkout.com task completed successfully.
CONNECTION MODEL
API key
Checkout.com Secret API Key from Developers > Keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Checkout.com.