Payhawk

payhawk.com

Payhawk declares 2 subprocessors, plus 1 of its own affiliates, in its subprocessor list, which we last checked on Nov 20, 2026 (evidence). They include Merge API. No published changes since we first read it on Sep 29, 2026.

Subprocessors CSV of Payhawk's subprocessors · Atom feed of Payhawk's subprocessors DORA draft CSV of Payhawk's subprocessors as declared by Payhawk what's this? · 

2 third parties, 1 affiliate.

NamePurposeLocationListed since
Duffel Technology Limited United Kingdom
Merge API, Inc. Sweden (AWS EU data centers)
Payhawk affiliates (1)
NamePurposeLocationListed since
Payhawk EOOD Belgium and Germany (LLMs hosted on Google Cloud)

Web TechnologiesCSV of Payhawk's web technologies · Atom feed of Payhawk's web technologies

Payhawk's homepage made 95 requests to 11 domains, and 4 services controlled by another company.

Advertising (1): MicrosoftAnalytics (1): CloudflareTag managers (1): Google CloudOther (1): Referral marketing: Cello

4 third parties by category: Advertising 1Analytics 1Tag managers 1Other 1

Third parties 4 · 53 requests
Google Cloud Google Tag Manager 32% of the page's requests 30
Microsoft Microsoft Advertising 13% of the page's requests 12
Cloudflare Cloudflare Browser Insights 11% of the page's requests 10
Cello Cello 1% of the page's requests 1
First party 1 · 42 requests
Payhawk Cloudflare Turnstile Google Analytics Google Cloud Google Cloud CDN Google Cloud Load Balancing HSTS HTTP/3 Microsoft Clarity Next.js 16.4.2 Next.js App Router Open Graph PWA Priority Hints React Swiper Turbopack Webpack 44% of the page's requests 42

3 tracked companies loaded by the homepage are not in Payhawk's subprocessor list. A website can use a service without it processing customer data.

Service statusCSV of Payhawk's status page incidents · Atom feed of Payhawk's status page incidents

Aug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: before our history of this status pageSep 27: before our history of this status pageSep 28: before our history of this status pageSep 29: before our history of this status pageSep 30: before our history of this status pageOct 1: before our history of this status pageOct 2: before our history of this status pageOct 3: before our history of this status pageOct 4: before our history of this status pageOct 5: before our history of this status pageOct 6: before our history of this status pageOct 7: before our history of this status pageOct 8: before our history of this status pageOct 9: before our history of this status pageOct 10: before our history of this status pageOct 11: before our history of this status pageOct 12: before our history of this status pageOct 13: before our history of this status pageOct 14: before our history of this status pageOct 15: before our history of this status pageOct 16: before our history of this status pageOct 17: before our history of this status pageOct 18: before our history of this status pageOct 19: before our history of this status pageOct 20: before our history of this status pageOct 21: before our history of this status pageOct 22: before our history of this status pageOct 23: before our history of this status pageOct 24: before our history of this status pageOct 25: before our history of this status pageOct 26: before our history of this status pageOct 27: before our history of this status pageOct 28: before our history of this status pageOct 29: before our history of this status pageOct 30: before our history of this status pageOct 31: before our history of this status pageNov 1: before our history of this status pageNov 2: no incident reportedNov 3: no incident reportedNov 4: no incident reportedNov 5: no incident reportedNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reportedNov 13: no incident reportedNov 14: no incident reportedNov 15: no incident reportedNov 16: no incident reportedNov 17: no incident reportedNov 18: no incident reportedNov 19: no incident reportedNov 20: no incident reportedNov 21: no incident reported

90 days agotoday

No incidents reported since Nov 2, 2026

As Payhawk's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Incidents reported by Payhawk's subprocessorsCSV of incidents reported by vendors Payhawk lists · Atom feed of incidents reported by vendors Payhawk lists

3 reported incidents in the last 30 days, by 1 of the vendors Payhawk lists as a subprocessor.

A subprocessor list names a company, not the service an incident touched. This does not show that Payhawk was involved.

DateCompanyIncidentImpactLasted
Merge APIDelayed webhook processing and tool-call logging no impact stated57 min
Merge APITemporary Rippling Integration Downtime no impact stated30 h 50 min
Merge APIInvestigating — Microsoft Integrations no impact stated20 h 3 min

Who is around them.

ChangesCSV of Payhawk's changes · Atom feed of Payhawk's changes

See the list as we read it on any date: Time machine

None since tracking began.

Rating badge for Payhawk's site

Payhawk transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/payhawk"><img src="https://thirdpartyindex.com/badge/payhawk.svg" alt="Payhawk transparency rating on Third Party Index" height="20"></a>
[![Payhawk transparency rating on Third Party Index](https://thirdpartyindex.com/badge/payhawk.svg)](https://thirdpartyindex.com/vendors/payhawk)