Skip to content
Accounting and finance ⇄ Database

Adyen to SAP Hana integration — real-time, two-way sync

Keep Adyen and SAP Hana in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Adyen and SAP Hana

Work with Adyen's financial data straight from SAP Hana: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Stores, Users and API Credentials, Webhook Configurations, Settlement Detail Reports from Adyen into SQL views, Schemas, Sequences, Triggers in SAP Hana and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against SAP Hana, and rows your code writes or updates flow back into Adyen with validation, so the finance system stays the system of record.

Common use cases

  • 01 Create Adyen Payment Links from an invoicing or billing system and sync each link's paid or expired status back so accounts receivable sees payment without opening the Customer Area.
  • 02 Provision Stores, Users, and API credentials through the Management API from an internal admin app or IdP so new locations and staff get the right Adyen access automatically.
  • 03 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
  • 04 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.

Common sync patterns

Write back safely

Updates written to the synced tables in SAP Hana propagate into Adyen, so automations can create or correct finance records without custom integration code.

React to financial events

Changes in Adyen appear in SAP Hana as row changes, so you can trigger downstream logic with the database tooling you already use.

Query finance data like any other data

Customers, invoices, and payments from Adyen live in SAP Hana as regular tables or collections your team can join, index, and query.

What you can sync between Adyen and SAP Hana

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Adyen objects SAP Hana objects How this pairing syncs
Modifications (Captures, Refunds, Cancels) Actions on an authorized payment via /payments/{pspReference}/captures, /refunds, and /cancels; written to settle, return, or void funds, with results confirmed by CAPTURE and REFUND webhooks. Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. Modifications (Captures, Refunds, Cancels) is specific to Adyen and Calculation views to SAP Hana — each maps to any object or custom field on the other side.
Payment Links Hosted payment link objects created through /paymentLinks; created, retrieved, and expired, with paid or expired status reported back through webhooks for accounts-receivable sync. SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. Payment Links is specific to Adyen and SQL views to SAP Hana — each maps to any object or custom field on the other side.
Merchant Accounts Company and merchant account entities in the Management API; read and updated to keep account configuration, payment-method settings, and capabilities aligned with internal systems. Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. Merchant Accounts is specific to Adyen and Schemas to SAP Hana — each maps to any object or custom field on the other side.
Stores Physical and online store entities under a merchant account (Management API); full CRUD, so new locations and their payment-method configuration can be provisioned from an internal admin source. Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. Stores is specific to Adyen and Sequences to SAP Hana — each maps to any object or custom field on the other side.
Users and API Credentials Customer Area users and API-credential objects managed via the Management API; created, updated, and deprovisioned to keep Adyen access aligned with an IdP or HR source. Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. Users and API Credentials is specific to Adyen and Triggers to SAP Hana — each maps to any object or custom field on the other side.
Webhook Configurations Per-company or per-merchant webhook subscriptions (Management API); created, listed, and updated to control which events Adyen sends and to which endpoint and HMAC key. System-versioned temporal tables Column store tables with a history table tracking each row's validity period; used to reconstruct update and delete history for change capture. Webhook Configurations is specific to Adyen and System-versioned temporal tables to SAP Hana — each maps to any object or custom field on the other side.

How changes propagate between Adyen and SAP Hana

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Adyen SAP Hana Sub-second propagation

DetectionAdyen notifies Stacksync of record changes through webhook events. Standard webhooks for payment events (AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and more) plus Management, Balance Platform, and report webhooks.

DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.

SAP Hana Adyen Sub-second propagation

DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.

DeliveryEach detected change is written to Adyen through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Adyen: Adyen does not publish fixed numeric rate limits; excessive requests return HTTP 429, and the Management API reports 'too many requests' in the error detail. Adyen recommends exponential backoff, and no rate-limit response headers are documented.
  • SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
What ships with Adyen ⇄ SAP Hana

Connect Adyen and SAP Hana for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Adyen–SAP Hana connection.

Real-time

Two-way sync

Changes in Adyen or SAP Hana instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Adyen or SAP Hana data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Adyen or SAP Hana record.

Observability

Monitoring

Track your Adyen ⇄ SAP Hana sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Adyen and SAP Hana.

How the Adyen and SAP Hana connectors work

Adyen

Integration surface
REST APIs on adyen.com - Checkout (/checkout/v71), Management (/v3), Balance Platform / Configuration, Transfers, Payouts, and Reports, with standard webhooks for events
Authentication
API key in the X-API-Key header per web service or Balance Platform user (primary for Checkout, Management, and Balance Platform); Basic auth for classic web-service users; OAuth 2.0 for partner integrations; client keys are client-side only
Change detection
Standard webhooks for payment events (AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and more) plus Management, Balance Platform, and report webhooks; all HMAC-signed and acknowledged with a 2xx within about 10 seconds. No database-style CDC; historical transactions come from Settlement Detail Reports
Capabilities
read · write · webhooks
Rate limits
Adyen does not publish fixed numeric rate limits; excessive requests return HTTP 429, and the Management API reports 'too many requests' in the error detail. Adyen recommends exponential backoff, and no rate-limit response headers are documented.

SAP Hana

Integration surface
SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
Authentication
Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
Change detection
Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
Capabilities
read · write · CDC
Rate limits
No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
How it works

How to connect Adyen to SAP Hana — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Adyen and SAP Hana with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Adyen connected
    SAP Hana connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Adyen and SAP Hana objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Adyen ⇄ SAP Hana
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Adyen SAP Hana
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Adyen and SAP Hana integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 535 integrations available for Adyen and SAP Hana.

Popular · 8 of 535
All Adyen integrations All SAP Hana integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own