About Composer

Composer is a single integration for managing fraud, identity, and payment transactions on any application. Composer protects your application by tracking visitors (this is optional) and by executing checkpoints at any key moment, such as account opening, login, or payment.

The tracking service collects device data, network information, and user session details. The Customer Data Platform (CDP) combines this with past session information and the results of executed checkpoints.

Checkpoints determine if an interaction should be allowed or denied and whether any follow-up response is needed. A no-code workflow builder (Checkpoint Studio) lets you automate that response based on tracked visitor data, signals from your application, and an Integration Catalog of payment service providers, fraud vendors, security tools, and more.

When to use Composer

Composer secures any risky action. A risky action is one that may open your application up to fraud from bad actors. Some key examples are:

• Registration: bad actors may create accounts programmatically.
• Login: bad actors may use stolen or guessed credentials to take over an account.
• Payments: bad actors may drain value from other users or use your application to launder money.
• Posting a Listing: bad actors may fill your application with spam, prohibited content, or defraud other users.
• Promotions: bad actors may act on both sides of a transaction (i.e. buyer-seller collusion) to extract value from your application.

But that's not where it stops. All applications, especially new ones, have unknown vulnerabilities waiting to be discovered. Composer is a toolkit designed to allow you to quickly address any new fraud discovered in your application.

Running payments in a checkpoint

Checkpoints aren't limited to fraud decisioning – the same canvas can run the payment itself. A transaction-processing checkpoint chains steps like Get Payment Method Info, Authorization, Capture, or Purchase alongside whatever fraud, identity, or 3DS logic you want, so a single checkpoint can score a transaction and execute it in one flow. See Transaction processing and Building a transaction processing checkpoint for the details.