Impulsify Cloud API Payment Demo for Adyen

1 · Impulsify UI 2 · Impulsify Backend 3 · Adyen Cloud 4 · Terminal

👇 Click each option below to compare Good vs. Bad on the live diagram

🖥️
Impulsify POS / UI
Amount + POIID

📦
Impulsify Backend + SDK
Holds X-API-Key · Typed Nexo

☁️
Adyen Cloud
/sync endpoint

💳
Payment Terminal
Tap · PIN · Auth

Decision factor for Impulsify	★ Option A · Backend + SDK (Recommended)	Option B · Backend Direct REST	Option C · Direct from UI
API Key Security	✓ Safe on Impulsify server	✓ Safe on Impulsify server	✕ Leaked in browser
Browser CORS	✓ Works (calls own backend)	✓ Works (calls own backend)	✕ Blocked by Adyen
Region & URL Routing	✓ Auto (TEST / US / EU)	⚠ Set URL per env	✕ Exposed
Payload Effort	✓ Typed SaleToPOI helpers	✓ Plain JSON (Copy cURL on main page)	✕ Unsafe
Best Fit for Impulsify	★ Best default if Node / Java / .NET	Any stack or zero-dependency preference	Never in production

1 · What Adyen provisions for Impulsify Own merchantAccount, Web Service X-API-Key (PAL + Cloud Device roles), and boarded terminal POIIDs.

2 · What Impulsify builds 2 backend endpoints: POST /payment (sends SaleToPOIRequest) and POST /abort (cancels in-flight ServiceID).

3 · What CHEQ learned in prod Keep HTTP timeout ≥ 150s, generate a unique 10-char ServiceID per call, and store POITransactionID for refunds.

Connection

API

Terminal Cloud What CHEQ uses Cloud Device Latest Adyen API

Merchant account Terminal (POIID)

Environment

Sale ID

New Sale ID after each request

API key & advanced

API key

LIVE region

Collect payment

Test scenario

Amount

What the terminal returned

Send a payment to see a plain-language summary of the Adyen response.

Raw request

Re-running manually? Change MessageHeader.ServiceID (1–10 chars, unique per 48h) and SaleTransactionID.TransactionID on each call — otherwise the terminal returns Repeated DB Message: ServiceID. Copy cURL auto-generates fresh IDs each click.

Outgoing SaleToPOIRequest appears here.

Raw response