Can Checkout.com and AMPECO talk in both directions?

Yes. Build one flow that starts in Checkout.com and acts in AMPECO, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect Checkout.com to AMPECO

Move data between Checkout.com and AMPECO the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore Checkout.com Explore AMPECO

Checkout.com triggers: 2
Checkout.com actions: 7
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with Checkout.com and AMPECO

A few flows teams run between Checkout.com and AMPECO. Use one as a starting point, or build your own from scratch.

Payment Events in Checkout.com creates Custom API Call in AMPECO
Trigger order fulfillment when payment is approved.
New notification in AMPECO creates Create Customer in Checkout.com
Triggers when a webhook notification event is received from Ampeco
Payment Events in Checkout.com creates Actions - Charge Point - Change Availability in AMPECO
Trigger order fulfillment when payment is approved.
New notification in AMPECO creates Update Customer in Checkout.com
Triggers when a webhook notification event is received from Ampeco
Payment Events in Checkout.com creates Actions - Charge Point - Change Owner in AMPECO
Trigger order fulfillment when payment is approved.
New notification in AMPECO creates Create Payment Link in Checkout.com
Triggers when a webhook notification event is received from Ampeco