UAT·Ops About UAT-Ops

Payment gateways for commercetools

Gateway pages

About commercetools

commercetools is a hosted, API-first commerce platform: carts, orders, products, customers and payments are exposed as REST and GraphQL resources, and the storefront is whatever the merchant builds on top. It is sold to mid-market and enterprise retailers, usually through systems integrators, and there is nothing to install locally.

Payments are deliberately outside the platform. The Payment API stores a payment, its PSP interface details and a list of transactions (authorization, charge, refund, cancel) with their states, but the money moves at an external payment service provider. The bridge between the two is a Connect connector: a small application pair hosted by commercetools, made of an "enabler" that serves the storefront payment component and a "processor" that calls the PSP, receives its webhooks and writes the resulting transactions back onto the Payment. An Organization administrator installs a connector from the Connect marketplace inside the Merchant Center, picks the region and Projects, and enters the connector's configuration, typically a commercetools API client plus the PSP's keys and webhook secret. Public marketplace connectors go through commercetools certification; connectors published for a single Organization do not. commercetools maintains the Adyen and PayPal connectors, Stripe maintains its own, and a PSP without a connector is integrated by cloning the open-source payment-integration template and implementing its authorization, capture, cancel and refund endpoints.

commercetools Checkout, a separate product with full-checkout and payment-only modes, consumes those same connectors as its Payment Integrations. For integration testing, every new Project starts a 60-day, no-card trial with the core APIs and Merchant Center; a gateway's own sandbox credentials are supplied when the connector is installed.

How payments work on commercetools

Third-party gateways
commercetools does not process payments. The Payment API records payments and transactions, and an external PSP does the financial work through a PSP-specific integration. Gateway integrations ship as Connect connectors: small hosted applications (an "enabler" for storefront components and a "processor" that talks to the PSP and writes transactions back) that an Organization administrator installs from the Connect marketplace in the Merchant Center, choosing region and Projects and filling in the connector's configuration values. Public marketplace connectors must pass commercetools certification (functionality, security, deployment compatibility, documentation); private/Organization connectors skip certification. commercetools builds the Adyen and PayPal connectors itself; Stripe maintains its own. A connector that uses a third-party service may require a commercial contract with that provider. The pricing page lists connectors among add-on services with no figures; no commercetools transaction fee for using an outside PSP appears in the pricing page or Connect documentation fetched on 2026-09-11.1
Checkout extensibility
commercetools Checkout runs in Complete Checkout or Payment Only mode and takes its PSPs from installed Connect connectors. Unsupported PSPs are added by building an Organization connector from the open-source payment-integration template, whose processor must implement authorization, capture, cancellation and refund and which is declared Checkout-compatible.2

What we checked

  • The Payment resource tracks PSP details, methods, transactions and state; the actual financial process runs at an external PSP connected by PSP-specific integrations.1
  • Connect hosts JavaScript/TypeScript or Java applications without the customer running infrastructure; a client deploys a published Connector via the Connect API, Merchant Center or CLI by creating a Deployment with configuration values.3
  • Publishing with certification true submits a Connector for marketplace listing; publishing with certification false restricts it to listed private Projects and needs no certification. Deployments queue and usually finish within 15 minutes.4
  • The Connect team certifies public Connectors for functional completeness, absence of security vulnerabilities (no hardcoded credentials, no insecure dependencies), deployment compatibility and full documentation; certified creators must fix critical vulnerabilities within 15 business days and high within 30.5
  • Organization Administrators install a public Connector from the Connect marketplace in the Merchant Center by choosing region and Projects, entering its configuration fields and clicking Install; public Connectors that call third-party services may require a commercial contract with that provider.6
  • Checkout requires at least one installed Connector to define Payment Integrations; public payment Connectors are built by commercetools (Adyen, PayPal) or third parties (Stripe), and custom PSPs need an Organization Connector built from the payment-integration template.2
  • The payment-integration template (github.com/commercetools/connect-payment-integration-template) has an enabler that serves storefront components and a processor exposing authorization, capture, cancellation and refund; it is Checkout-compatible.7
  • Checkout offers Complete Checkout and Payment Only modes, integrates PSPs and gift-card systems through Connect marketplace connectors, and is PCI DSS compliant.8
  • The Adyen payment connector is an MIT-licensed repository in the commercetools GitHub organization, deployed through Connect with enabler and processor modules, covering cards, SEPA, Apple Pay, Google Pay, PayPal, iDEAL and Bancontact with HMAC-verified webhooks.9
  • The commercetools technology-partner listing states the Adyen integration was built by commercetools together with Adyen.10
  • The Stripe connector is selected from the Connect Marketplace, scoped to region, organization and projects, then configured with commercetools API-client variables and the Stripe secret key, webhook id and webhook signing secret; it exposes an enabler URL and a processor URL that receives Stripe webhooks.11
  • Stripe maintains its commercetools Connect app under the stripe GitHub organization under the MIT license, with enabler and processor modules and support for Apple Pay, Google Pay, Amazon Pay and subscriptions.12
  • The 60-day free trial needs no credit card, gives access to the core commerce APIs and Merchant Center with sample data, does not convert automatically, and excludes products such as InStore, Frontend and agentic capabilities.13
  • The sign-up guide states every new Project gets a 60-day trial, started from the Merchant Center via Create new Account, with hosting on GCP and AWS in North America and Europe and GCP in Australia.14
  • The pricing page describes custom, order-based packages rather than GMV fees, lists connectors among add-on services, and publishes no figures or per-transaction charges.15
  • Connect applications are written in JavaScript/TypeScript (recommended) or Java and declared in connect.yaml as service, job, event, Merchant Center custom application/view or assets types.16

Sources

  1. https://docs.commercetools.com/api/projects/paymentsofficial documentation · checked 2026-09-11
  2. https://docs.commercetools.com/checkout/connectors-and-applicationsofficial documentation · checked 2026-09-11
  3. https://docs.commercetools.com/connect/overviewofficial documentation · checked 2026-09-11
  4. https://docs.commercetools.com/connect/getting-startedofficial documentation · checked 2026-09-11
  5. https://docs.commercetools.com/connect/certificationofficial documentation · checked 2026-09-11
  6. https://docs.commercetools.com/merchant-center/connectofficial documentation · checked 2026-09-11
  7. https://docs.commercetools.com/connect/templates/payment-integrationofficial documentation · checked 2026-09-11
  8. https://docs.commercetools.com/checkout/overviewofficial documentation · checked 2026-09-11
  9. https://github.com/commercetools/connect-payment-integration-adyencode repository · checked 2026-09-11
  10. https://commercetools.com/technology-partners/adyenpartner directory · checked 2026-09-11
  11. https://docs.stripe.com/connectors/commercetools-connect/install-and-configureofficial documentation · checked 2026-09-11
  12. https://github.com/stripe/stripe-commercetools-connect-appcode repository · checked 2026-09-11
  13. https://commercetools.com/free-trialvendor pricing page · checked 2026-09-11
  14. https://docs.commercetools.com/api/getting-started/initial-setupofficial documentation · checked 2026-09-11
  15. https://commercetools.com/pricingvendor pricing page · a claim here is implied by this source, not stated · checked 2026-09-11
  16. https://docs.commercetools.com/connect/developmentofficial documentation · checked 2026-09-11

Last verified 2026-09-11 · Reviewed by a person 2026-09-25

Integration capabilities, requirements, pricing, availability, and vendor policies may change over time. UAT-Ops documents information based on the authoritative sources and testing available at the time of review.

Where newer information, testing, or vendor documentation materially changes a published claim, UAT-Ops may revise the page to reflect the most current verified information. Readers should confirm time-sensitive requirements with the relevant vendor before making production or purchasing decisions.