Skip to content
Accounting and finance ⇄ Business productivity

Adyen to Microsoft Teams integration — real-time, two-way sync

Keep Adyen and Microsoft Teams 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 Microsoft Teams

Connect the financial records in Adyen with the work happening in Microsoft Teams, so both stay current without exports or copy-paste.

Adyen holds the financial truth: who the customers are, what they were billed, what they paid. Microsoft Teams is where part of the day-to-day work happens, and that work often involves the same customers and transactions. Without a live connection, the two drift apart, and people end up answering questions from stale copies.

Stacksync keeps Payments, Modifications (Captures, Refunds, Cancels), Payment Links, Merchant Accounts in Adyen and Channels, Channel Messages, Chats & Chat Messages, Team Members & Users in Microsoft Teams in sync, bi-directionally and in real time. Whatever records Microsoft Teams keeps and whatever events it produces, the overlap with Adyen is mapped field by field, and a change on either side shows up on the other within seconds.

There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning running on yesterday's data.

Common use cases

  • 01 Trigger a capture, refund, or cancel on an Adyen payment when an order's state changes in a CRM, OMS, or ERP, and write the returned pspReference and status back onto the record.
  • 02 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.
  • 03 Route support case updates from the CRM into a triage channel for faster response.
  • 04 Archive channel messages into a warehouse for compliance and communication analytics.

Common sync patterns

Where Microsoft Teams tracks people or companies: one identity

A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.

Where Microsoft Teams is a docs or knowledge workspace: reference data kept fresh

Figures teams rely on, like customer status or outstanding balances, stay current wherever Microsoft Teams surfaces them instead of going stale after a one-time paste.

Where Microsoft Teams handles customer conversations: billing context in view

Front-line teams see invoice and payment status from Adyen next to the customer they are helping, without logging into the finance system.

What you can sync between Adyen and Microsoft Teams

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 Microsoft Teams objects How this pairing syncs
Settlement Detail Reports Downloadable reports of settled transactions, fees, and payouts per merchant account; read-only, delivered when a report webhook fires, and loaded for finance reconciliation. Team Members & Users Membership synced with identity, HR, or CRM ownership data. Settlement Detail Reports is specific to Adyen and Team Members & Users to Microsoft Teams — each maps to any object or custom field on the other side.
Payments Checkout API payment requests and results (/payments); created to authorize a card, wallet, or local payment, and retrieved by pspReference. Final state arrives asynchronously via the AUTHORISATION webhook. Online Meetings Meeting records synced with scheduling and CRM activity timelines. Payments is specific to Adyen and Online Meetings to Microsoft Teams — each maps to any object or custom field on the other side.
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. Tabs & Installed Apps App configuration read to audit or provision team workspaces. Modifications (Captures, Refunds, Cancels) is specific to Adyen and Tabs & Installed Apps to Microsoft Teams — 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. Teams Team containers provisioned or read to mirror org and project structure. Payment Links is specific to Adyen and Teams to Microsoft Teams — 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. Channels Channel targets used for routing synced notifications and updates. Merchant Accounts is specific to Adyen and Channels to Microsoft Teams — 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. Channel Messages Posted messages read for archiving or written to broadcast record changes. Stores is specific to Adyen and Channel Messages to Microsoft Teams — each maps to any object or custom field on the other side.

How changes propagate between Adyen and Microsoft Teams

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 Microsoft Teams 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 written to Microsoft Teams through its API, with automatic retries and rate-limit backoff.

Microsoft Teams Adyen Sub-second propagation

DetectionMicrosoft Teams notifies Stacksync of record changes through webhook events. Graph change notifications (webhooks) for messages and membership.

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.
What ships with Adyen ⇄ Microsoft Teams

Connect Adyen and Microsoft Teams for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Adyen or Microsoft Teams 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 Microsoft Teams record.

Observability

Monitoring

Track your Adyen ⇄ Microsoft Teams 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 Microsoft Teams.

How the Adyen and Microsoft Teams 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.

Microsoft Teams

Integration surface
REST API (Microsoft Graph)
Authentication
OAuth 2.0 via Microsoft Entra ID; reading message content at scale requires Microsoft-approved protected-API access
Change detection
Graph change notifications (webhooks) for messages and membership; delta queries on some resources
Capabilities
read · write · webhooks
How it works

How to connect Adyen to Microsoft Teams — 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 Microsoft Teams 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
    Microsoft Teams connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Adyen and Microsoft Teams 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 ⇄ Microsoft Teams
    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 Microsoft Teams
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Adyen and Microsoft Teams 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 440 integrations available for Adyen and Microsoft Teams.

Popular · 8 of 440
Coworkers laughing in front of a laptop in a casual office setting

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