Checkout Releases

The Checkout Transactions API is now available in public beta. With this new API, you can initiate payments managed by Checkout without using the Checkout UI. For example, you can leverage the API to process recurring payments for subscription-based orders.

Sending a Create Transaction request is equivalent to a customer confirming a payment on the UI. When you create a Transaction, the payment Connector sends the request to the payment service provider (PSP) to process the payment for a specific Cart. Then, Checkout verifies that the Payment amount matches the total of the Cart, and creates an Order from the Cart.

Setting custom Order numbers in Checkout Sessions is now available in public beta.

When creating a Checkout Session, you can now set a custom Order number to let you manage and track orders consistently across your platforms, payment service providers, and customer communications. You can set the Order number using the new optional futureOrderNumber field, and it is then stored in the Composable Commerce Order entity.

Checkout Messages now contain the correlationId field, which helps you with debugging and message traceability. To receive Messages containing this field, you must use the latest version of the Checkout Browser SDK.

Checkout is now available as a built-in application in the Merchant Center. This provides easier access to the application and reduces the setup time. Previously, you had to manually install the application for each Project or Organization.

Additionally, we’ve repositioned Checkout in the Merchant Center main menu, placing it between Discounts and Audit Log.

Checkout is now available in North America on Azure Virginia, in addition to the existing Regions available on Google Cloud Platform (GCP). For more information, see Hosts.

Checkout now supports the drop-in Payment Integration Type in public beta.

With the drop-in Payment Integration Type, you can render payment methods on the checkout page of your Application through a single pre-built UI element containing all methods. This Payment Integration Type requires little configuration from the Merchant Center because the rendering of payment methods on the page totally depends on the payment service provider (PSP) and on your PSP account settings.

Checkout supports the drop-in Payment Integration Type for Adyen via the dedicated Public Connector and for custom PSPs via Organization Connectors.

Checkout now supports the Czech, Romanian, and Slovak locales. Additionally, you can now use purchase order as a payment method with the sample payment Connector.

We have made the following changes to the Messages sent by commercetools Checkout. Messages provide feedback about events during the payment process, helping you inform customers and manage different scenarios that may occur. You can subscribe to Messages using the Checkout Browser SDK.

Changes:

• Added AddDiscountCodeError Message.
• Added RemoveDiscountCodeError Message.
• Added DiscountCodeNotApplicable Message.
• Added ShippingAddressMissingError Message.
• Added ShippingMethodDoesNotMatchCart Message.
• Added InvalidLocale Message.
• Added BadInputData Message.
• Added UpdatedFields Message.
• Replaced InvalidToken Message with ExpiredSession Message.
• Removed ApplicationNotFound and NoPermissionsFound Messages.

commercetools Checkout now supports the following payment methods via Adyen:

• Bancontact card
• Bancontact mobile
• Electronic Payment Standard (EPS)
• Single Euro Payments Area (SEPA)
• TWINT

You can now offer your customers a broader choice of payment methods and thus improve your checkout experience.

The activation of commercetools Checkout now happens automatically when adding Checkout to your Project as a Custom Application. This speeds up the setup process as you no longer need to contact the Checkout support team to activate Checkout.

commercetools Checkout now supports the following payment methods via Adyen:

• Apple Pay
• Google Pay
• Klarna Pay now
• Klarna Pay later
• Klarna Pay over time

You can now customize the labels and descriptions of your custom payment methods, which you configure through Organization Connectors.

By default, a custom payment method has no description and its label is the key provided by the payment Connector. Previously, you could not edit the label nor add a description. Now, you can customize the related properties like you can for standard payment methods. This helps you show your customers better text on the checkout page.

Payment method predicates are now available in public beta. When creating or editing an Application, you can now enter predicates to determine the conditions for displaying each payment method of your Application.
For example, you can set a predicate to display PayPal among the available payment methods only if the amount of the cart is at least 10 Euro.

Payment method predicates are conditional statements that operate on a true/false logic and they are evaluated against the values of the Cart fields, including Custom Fields. If the predicate evaluates as true, the payment method is displayed; otherwise, the payment method is not displayed.

The Payment Only mode is now available in public beta. With the Payment Only mode, you can integrate only the payment functionality of commercetools Checkout without changing the existing checkout flow on your storefront.
In fact, the mode lets you take advantage of Checkout's secure and seamless payment capabilities without having to adjust other elements of your existing checkout experience, such as address forms or success and failure pages.

To use Checkout in Payment Only mode, you need to:

• Create at least one Application of the Payment Only type.
• Call the paymentFlow SDK method to initialize Checkout.

If required, you can create Applications of both the Payment Only type and the Complete checkout type for the same Project but for different countries or URLs.

commercetools Checkout now leverages Connectors from commercetools Connect. Additionally, the Checkout Browser SDK underwent some changes.

We introduced the confirmation of permissions and a subscription in public beta to let Checkout access and update your Composable Commerce data. With permissions, Checkout can create a Composable Commerce API Client using specific scopes, while the subscription lets Checkout update Composable Commerce data according to the status of payments.

commercetools Checkout is now available in Australia on Google Cloud Sydney. This expansion complements our presence in Europe and North America Regions, offering Checkout's capabilities to merchants in Australia.

You can now customize the layout of commercetools Checkout's address forms by adding, removing, and reordering fields. To do so, you can use standard fields and configure custom fields that suit your use case.
Additionally, you can customize the address summary to match your custom address forms.

This new feature helps you tailor the address forms and summary in your checkout experience to your business scenario.

Checkout Payments API is now available in public beta. This new feature lets you easily manage actions on payments, such as payment capture, refund, and authorization cancellation.

Following your request via the Checkout Payments API, Checkout will request the payment service provider (PSP) to perform the related financial process to capture or refund a given amount to the customer, or to cancel the authorization for a payment. This saves you time and effort in managing payment operations.

The sellerId, applicationId, and callbackUrl configuration fields are now deprecated. You now need to use the projectKey, applicationKey, and returnUrl fields respectively.
The new DeprecatedFields message will warn you if you use any of the deprecated fields.
Also, following the deprecation, the ProjectIsDeactivated message replaced the SellerIsDeactivated one, while a standard CORS error in the browser will replace the SellerNotFound message.

In addition, further new messages are available to receive feedback from more events.

With the invoice payment connector, you can now offer payment by invoice to your customers, thus automating the reception of their requests to pay by invoice.
To activate payment by invoice on your checkout page, configure the invoice payment connector and then set the payment method in your application.

You can now display tax information from Composable Commerce in the price summary of your checkout page using the showTaxes configuration property.

Additionally, you can now manage the currency format of prices using the currencyLocale configuration property.

You can now display the commercetools Checkout UI component inline with your content, such as a custom header or footer. This gives you flexibility in managing the appearance of your checkout experience. Previously, the Checkout UI component appeared full screen and hid the content on your page, which is also the default behavior.

For more information, see Checkout Browser SDK.

When specifying dynamic parameters, you must now use single curly braces instead of double curly braces. For example, {PARAMETER_NAME} instead of {{PARAMETER_NAME}}.

The Text and labels documentation is updated and reflects this change.

You can now display or hide the field for entering discount codes on your checkout page. To do so, use the Activation of discount code function toggle in the Application settings section when creating or editing an Application.

You can now subscribe to notifications for your PayPal payment connector. To provide notifications about the status of the payment process, PayPal uses webhooks to call back the commercetools Checkout application.

By adding a mock payment connector, you can now run your checkout flow from start to finish for test purposes or proofs of concept, with few configuration steps and without connecting to a payment service provider (PSP).

The mock payment connector is not available by default. To activate it for your Project, contact the Checkout support team.

After collecting feedback during the closed beta phase, we have moved commercetools Checkout to general availability. With Checkout, you can:

• Create a one-page checkout with minimal development effort.
• Reduce API calls; Checkout is powered by Composable Commerce for adaptability and efficiency.
• Free yourself from compliance concerns; Checkout is PCI DSS-compliant for secure payment handling.
• Integrate seamlessly with industry-leading payment service providers (PSPs).
• Customize and localize your checkout experience to display local currencies, automate regional tax calculations, and offer multi-language support.
• Create rule-based routing for personalized checkout experiences.
• Subscribe to real-time event messages for continuous improvement and enhanced customer experiences.

To get access to Checkout, contact the Checkout support team.