Skip to content
Accounting and finance ⇄ E-commerce

Adyen to Easypost integration — real-time, two-way sync

Keep Adyen and Easypost 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 Easypost

Turn every Easypost order into clean revenue: Adyen and Easypost keep customers, orders, and payment status aligned in real time, in both directions.

Easypost runs the storefront — the catalog, the orders, and the buyers placing them. Adyen records the money behind those orders — invoices, revenue, payments, and the ledger the business closes on. The overlap is every customer, order, and product both sides need to agree on, and when that overlap is bridged by CSV export or an overnight batch, finance reconciles against stale numbers while the store quotes prices or stock the books no longer recognize.

Stacksync syncs Merchant Accounts, Stores, Users and API Credentials, Webhook Configurations in Adyen with Rate, Tracker, Batch, CarrierAccount in Easypost field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Easypost, its paid-or-overdue state from Adyen — and Stacksync keeps every copy consistent and resolves conflicts by the rules you set.

The result is one shared record of who bought what and whether it has been paid, so the storefront, support, and the finance team all read from the same current data instead of re-keying it between systems.

Common use cases

  • 01 Ingest AUTHORISATION, CAPTURE, REFUND, and CHARGEBACK webhooks into Postgres or a warehouse so finance reconciles Adyen settlements against orders in an ERP without manual report exports.
  • 02 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.
  • 03 When an order is ready to ship in an OMS, ERP, or database, create an EasyPost Shipment, buy the lowest qualifying Rate, and write the label URL and tracking code back onto the order.
  • 04 Create a Tracker for every outbound shipment and stream tracker.updated webhook events into Postgres or a warehouse so support and ops see live delivery status beside order records.

Common sync patterns

Where Easypost originates orders: sales flow into the books

A new or updated order in Easypost creates or updates the matching invoice or revenue record in Adyen, so billing and reporting start without re-entry.

Where Adyen is the money system of record: payment status on the order

Paid, overdue, and refunded state from Adyen lands on the order or account in Easypost, so the store and support see what has actually been collected.

One customer master

Where both systems keep customer or buyer records, an edit in either propagates to the other, ending duplicate accounts and mismatched contact details.

What you can sync between Adyen and Easypost

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 Easypost objects How this pairing syncs
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. Batch Bulk shipment processing; create a batch, add or remove shipments, buy all labels at once, and generate a consolidated label or ScanForm for the day's orders. Payment Links is specific to Adyen and Batch to Easypost — 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. CarrierAccount Carrier credentials and settings that control which carriers and negotiated rates are available; create, update, and delete to manage enabled carriers across accounts. Merchant Accounts is specific to Adyen and CarrierAccount to Easypost — 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. Webhook Event subscriptions delivering an Event via HTTP POST on object changes; full CRUD (create, retrieve, list, update, delete) and the mechanism for near-real-time change delivery to Stacksync. Stores is specific to Adyen and Webhook to Easypost — 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. Shipment The central writable object: create with a to/from Address and Parcel, receive Rate options, then buy a label to get postage_label and tracking_code; retrieve and list with cursor pagination. Users and API Credentials is specific to Adyen and Shipment to Easypost — 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. Address Origin and destination locations; create, retrieve, and list, plus address verification (delivery and residential) to normalize and validate addresses before they are saved downstream. Webhook Configurations is specific to Adyen and Address to Easypost — each maps to any object or custom field on the other side.
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. Parcel Package dimensions and weight (or a predefined_package); created standalone or inline on a Shipment and reused across shipments and batches. Settlement Detail Reports is specific to Adyen and Parcel to Easypost — each maps to any object or custom field on the other side.

How changes propagate between Adyen and Easypost

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

Easypost Adyen Sub-second propagation

DetectionEasypost notifies Stacksync of record changes through webhook events. Webhooks deliver an Event via HTTP POST on object changes (e.g.

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.
  • Easypost: Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests.
What ships with Adyen ⇄ Easypost

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Easypost

Integration surface
REST API (EasyPost API v2, https://api.easypost.com/v2)
Authentication
HTTP Basic auth with the API key as the username and an empty password (Bearer token also accepted); separate Test and Production keys
Change detection
Webhooks deliver an Event via HTTP POST on object changes (e.g. tracker.updated); historical pulls via list/index endpoints using before_id/after_id cursor pagination
Capabilities
read · write · webhooks
Rate limits
Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests
Easypost setup guide
How it works

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

    Choose tables

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

Adyen and Easypost 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
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 459 integrations available for Adyen and Easypost.

Popular · 8 of 459
All Adyen integrations All Easypost 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