Skip to content
← Back to documentation
Technical Reference

Checkout.com

Checkout.com integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 29, 2026

Overview

Connect Checkout.com with Flows360

Checkout.com integration for Flows360 workflows.

Use the Checkout.com connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and 2 triggers.

Available actions

  • Create Customer
  • Update Customer
  • Create Payment Link
  • Create Payment
  • Refund a Payment
  • Get Payment Details
  • Get Payment Actions

Available triggers

  • Payment Events
  • Dispute Events

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Checkout.com
  • Package: @activepieces/piece-checkout@0.1.7
  • Exact artifact digest: sha256:b9f875c4476f3dcceb83a37357fc28e3a47c5a50f9188ec889b936bbb986f01e
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Customer (create_customer), Store a customer's details in a customer object to reuse in future payments. You can link payment instruments and set a default instrument. Classification: read.
  • Update Customer (update_customer), Update existing customer or their metadata. Classification: read.
  • Create Payment Link (create_payment_link), Create a Payment Link to accept and process payment details. Classification: read.
  • Create Payment (create_payment), Process and manage payments from various sources including card payments and payouts. Classification: read.
  • Refund a Payment (refund_payment), Issue a refund (full or partial) for a captured payment. Supports split refunds, line items, and bank account destinations. Classification: read.
  • Get Payment Details (get_payment_details), Check transaction amount and status before refunding. Classification: read.
  • Get Payment Actions (get_payment_actions), Build full transaction lifecycles for audit logs. Classification: read.

Trigger contracts

  • Payment Events, webhook.
  • Dispute Events, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects9
Supported actions7
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Secret Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Customer Yes No Store a customer's details in a customer object to reuse in future payments. You can link payment instruments and set a default instrument.
Update Customer Yes No Update existing customer or their metadata.
Create Payment Link Yes No Create a Payment Link to accept and process payment details.
Create Payment Yes No Process and manage payments from various sources including card payments and payouts.
Refund a Payment Yes No Issue a refund (full or partial) for a captured payment. Supports split refunds, line items, and bank account destinations.
Get Payment Details Yes No Check transaction amount and status before refunding.
Get Payment Actions Yes No Build full transaction lifecycles for audit logs.
Payment Events Yes No webhook trigger declared by the pinned package.
Dispute Events Yes No webhook trigger declared by the pinned package.

Supported actions

Create Customer · Read

Store a customer's details in a customer object to reuse in future payments. You can link payment instruments and set a default instrument.

create_customer · Risk: low · Retry: safe

Inputs

  • email · string · Required, The customer's email address
  • name · string · Optional, The customer's name
  • phone_country_code · string · Optional, The international country calling code (e.g., +1, +44). Required if phone number is provided.
  • phone_number · string · Optional, The phone number (6-25 characters). Required if country code is provided.
  • metadata · object · Optional, Additional information about the customer. Maximum 10 key-value pairs, each up to 100 characters.
  • default · string · Optional, The ID of the payment instrument to set as this customer's default
Update Customer · Read

Update existing customer or their metadata.

update_customer · Risk: low · Retry: safe

Inputs

  • customerId · string · Required, The ID of the customer to update (e.g., cus_y3oqhf46pyzuxjocn2giaqnb44)
  • email · string · Optional, The customer's email address
  • name · string · Optional, The customer's name
  • phone_country_code · string · Optional, The international country calling code (e.g., +1, +44). Required if phone number is provided.
  • phone_number · string · Optional, The phone number (6-25 characters). Required if country code is provided.
  • metadata · object · Optional, Additional information about the customer. Will replace any existing metadata.
  • default · string · Optional, The ID of this customer's default instrument
Create Payment Link · Read

Create a Payment Link to accept and process payment details.

create_payment_link · Risk: low · Retry: safe

Inputs

  • amount · number · Required, The payment amount in minor units (e.g., cents for USD)
  • currency · string · Required, The three-letter ISO currency code (e.g., USD, EUR)
  • reference · string · Optional, A reference to identify the payment (e.g., order number)
  • description · string · Optional, A description of the payment
  • billing_country · string · Required, The two-letter ISO country code (e.g., US, GB)
  • billing_address_line1 · string · Optional, The first line of the billing address
  • billing_address_line2 · string · Optional, The second line of the billing address
  • billing_city · string · Optional, The billing address city
  • billing_state · string · Optional, The state or province (ISO 3166-2 code)
  • billing_zip · string · Optional, The billing address zip or postal code
  • billing_phone_country_code · string · Optional, The international country calling code (e.g., +1)
  • billing_phone_number · string · Optional, The phone number (6-25 characters)
  • customer_email · string · Optional, The customer's email address
  • customer_name · string · Optional, The customer's name
  • customer_phone_country_code · string · Optional, The international country calling code (e.g., +1)
  • customer_phone_number · string · Optional, The customer's phone number
  • expires_in · number · Optional, Time for which the link remains valid (default: 86400)
  • display_name · string · Optional, The merchant name to display to customers on the checkout page
  • return_url · string · Optional, URL to redirect customer after successful payment
  • locale · string · Optional, Language and region for the payment page
  • allow_payment_methods · array · Optional, Specific payment methods to present to customers
  • disabled_payment_methods · array · Optional, Payment methods to NOT present to customers
  • products · array · Optional, Details about the products in the order
  • shipping_country · string · Optional, The two-letter ISO country code for shipping
  • shipping_address_line1 · string · Optional, The first line of the shipping address
  • shipping_address_line2 · string · Optional, The second line of the shipping address
  • shipping_city · string · Optional, The shipping address city
  • shipping_state · string · Optional, The state or province for shipping
  • shipping_zip · string · Optional, The shipping address zip or postal code
  • payment_type · string · Optional, Type of payment for card transactions
  • processing_channel_id · string · Required, The processing channel to be used for the payment. Find this in your Checkout.com dashboard under Settings > Processing Channels. Format: pc_xxxxxxxxxxxxxxxxxxxxxxxxxx
  • capture · boolean · Optional, Whether to capture the payment immediately
  • enable_3ds · boolean · Optional, Whether to process as 3D Secure payment
  • challenge_3ds · string · Optional, Preference for 3DS challenge
  • metadata · object · Optional, Additional key-value pairs for transaction information
Create Payment · Read

Process and manage payments from various sources including card payments and payouts.

create_payment · Risk: low · Retry: safe

Inputs

  • currency · string · Required, The three-letter ISO currency code (e.g., USD, EUR)
  • amount · number · Optional, The payment amount in minor units (e.g., cents for USD). Use 0 for card verification.
  • reference · string · Optional, Your reference for the payment (e.g., order number)
  • description · string · Optional, A description of the payment
  • source_type · string · Required, The type of payment source
  • card_number · string · Optional, The card number (without separators). Required for card payments.
  • expiry_month · number · Optional, The expiry month of the card (1-12)
  • expiry_year · number · Optional, The expiry year of the card (4 digits)
  • cvv · string · Optional, The card verification code (3-4 digits)
  • cardholder_name · string · Optional, The name of the cardholder
  • customer_id · string · Optional, The customer ID (for customer source type, e.g., cus_y3oqhf46pyzuxjocn2giaqnb44)
  • token_id · string · Optional, The token ID (for token source type)
  • instrument_id · string · Optional, The instrument ID (for instrument source type)
  • billing_address_line1 · string · Optional, The first line of the billing address
  • billing_address_line2 · string · Optional, The second line of the billing address
  • billing_city · string · Optional, The billing city
  • billing_state · string · Optional, The billing state or province
  • billing_zip · string · Optional, The billing ZIP or postal code
  • billing_country · string · Optional, The two-letter ISO country code
  • billing_phone_country_code · string · Optional, The international country calling code (e.g., +1)
  • billing_phone_number · string · Optional, The phone number (6-25 characters)
  • account_holder_first_name · string · Optional, The first name of the account holder
  • account_holder_last_name · string · Optional, The last name of the account holder
  • account_holder_middle_name · string · Optional, The middle name of the account holder
  • customer_email · string · Optional, The customer's email address
  • customer_name · string · Optional, The customer's name
  • customer_phone_country_code · string · Optional, The international country calling code
  • customer_phone_number · string · Optional, The customer's phone number
  • shipping_first_name · string · Optional, The first name for shipping
  • shipping_last_name · string · Optional, The last name for shipping
  • shipping_email · string · Optional, The email for shipping notifications
  • shipping_address_line1 · string · Optional, The first line of the shipping address
  • shipping_address_line2 · string · Optional, The second line of the shipping address
  • shipping_city · string · Optional, The shipping city
  • shipping_state · string · Optional, The shipping state or province
  • shipping_zip · string · Optional, The shipping ZIP or postal code
  • shipping_country · string · Optional, The two-letter ISO country code for shipping
  • payment_type · string · Optional, The type of payment
  • capture · boolean · Optional, Whether to capture the payment immediately
  • authorization_type · string · Optional, The type of authorization
  • enable_3ds · boolean · Optional, Whether to process as 3D Secure payment
  • challenge_3ds · string · Optional, Preference for 3DS challenge
  • allow_3ds_upgrade · boolean · Optional, Process as 3DS if soft declined due to 3DS authentication required
  • enable_risk_assessment · boolean · Optional, Whether to perform risk assessment
  • customer_ip · string · Optional, The customer's IP address (IPv4 or IPv6)
  • processing_channel_id · string · Optional, The processing channel to use for the payment
  • previous_payment_id · string · Optional, Link to existing payment series (for recurring payments)
  • success_url · string · Optional, Success redirect URL for redirect payment methods
  • failure_url · string · Optional, Failure redirect URL for redirect payment methods
  • metadata · object · Optional, Additional key-value pairs for transaction information
Refund a Payment · Read

Issue a refund (full or partial) for a captured payment. Supports split refunds, line items, and bank account destinations.

refund_payment · Risk: low · Retry: safe

Inputs

  • reference · string · Required, A reference, such as an order ID, that can be used to identify the payment
  • payment_id · string · Required, Select the payment to refund
  • amount · number · Optional, The amount to refund in minor units. If not specified, full payment amount will be refunded.
  • refund_reference · string · Optional, Your reference for the refund (max 80 chars, 30 for Amex, 50 for TWINT)
  • capture_action_id · string · Optional, The action ID of the capture to refund (only for PayPal and Riverty)
  • amount_allocations · array · Optional, Split refund allocations for sub-entities
  • items · array · Optional, Order line items for the refund
  • destination_country · string · Optional, Two-letter ISO country code for bank account (required for giropay/EPS)
  • destination_account_number · string · Optional, The bank account number
  • destination_bank_code · string · Optional, The code that identifies the bank
  • destination_iban · string · Optional, International Bank Account Number
  • destination_swift_bic · string · Optional, 8 or 11-digit code identifying the bank
  • account_holder_first_name · string · Optional, The account holder's first name
  • account_holder_last_name · string · Optional, The account holder's last name
  • account_holder_type · string · Optional, The type of account holder
  • account_holder_company_name · string · Optional, Company name for corporate account holders
  • account_holder_email · string · Optional, The account holder's email address
  • account_holder_phone_country_code · string · Optional, International country calling code
  • account_holder_phone_number · string · Optional, The account holder's phone number
  • account_holder_address_line1 · string · Optional, First line of the account holder's address
  • account_holder_address_line2 · string · Optional, Second line of the account holder's address
  • account_holder_city · string · Optional, Account holder's city
  • account_holder_state · string · Optional, Account holder's state or province
  • account_holder_zip · string · Optional, Account holder's ZIP or postal code
  • account_holder_country · string · Optional, Two-letter ISO country code
  • bank_name · string · Optional, The name of the bank
  • bank_branch · string · Optional, The name of the bank branch
  • bank_address_line1 · string · Optional, First line of the bank's address
  • bank_address_line2 · string · Optional, Second line of the bank's address
  • bank_city · string · Optional, The bank's city
  • bank_country · string · Optional, Two-letter ISO country code for the bank
  • metadata · object · Optional, Additional key-value pairs for the refund request
Get Payment Details · Read

Check transaction amount and status before refunding.

get_payment_details · Risk: low · Retry: safe

Inputs

  • reference · string · Required, A reference, such as an order ID, that can be used to identify the payment
  • paymentId · string · Required, Select the payment to get details for
Get Payment Actions · Read

Build full transaction lifecycles for audit logs.

get_payment_actions · Risk: low · Retry: safe

Inputs

  • reference · string · Required, A reference, such as an order ID, that can be used to identify the payment
  • paymentId · string · Required, Select the payment to get actions for

Triggers

Payment Events · Webhook

Trigger order fulfillment when payment is approved.

Inputs

  • eventTypes · array
Dispute Events · Webhook

Notify operations upon dispute opening or resolution.

Inputs

  • eventTypes · array

Setup

Setup

  1. Add the Checkout.com connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-checkout@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Checkout.com connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-checkout@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.