AnkorPay - Security & Trust Overview

May 2026

Built on a Certified Stack

AnkorPay is built on infrastructure providers that carry the compliance certifications enterprise security teams require. Each provider was selected in part for its certification posture, so compliance coverage is built into the foundation of the platform.

ProviderRoleCertifications
AirwallexPayment processing & card issuingPCI DSS Level 1 · SOC 1 & 2 Type II · ISO 27001 · GDPR · DORA
KindeIdentity & authenticationSOC 2 Type II · ISO 27001
NeonDatabase infrastructureSOC 2 Type II · ISO 27001 · ISO 27701 · HIPAA · GDPR · CCPA
CloudflareEdge network & runtimeSOC 2 Type II · ISO 27001 · PCI DSS · FedRAMP

Full compliance reports (AOC, SOC 2 reports, penetration test summaries) are available from Airwallex on request.


AnkorPay Never Touches Your Card Data

AnkorPay is architecturally outside PCI scope for cardholder data.

  • No full card numbers are ever transmitted to or stored in AnkorPay's systems. Airwallex's API returns only masked card numbers (e.g. ****-****-****-1234), and that is the only format that exists in our database.
  • No CVV or sensitive authentication data is processed by AnkorPay at any point.
  • Viewing full card details happens inside a secure Airwallex-hosted iframe using a short-lived token. The raw PAN and CVV are rendered directly from Airwallex's infrastructure and never pass through AnkorPay's backend.
  • Card transactions are authorized and settled entirely within Airwallex's infrastructure. AnkorPay receives signed notification events and records transaction metadata (amount, merchant, date) for APA tracking purposes. Authorization and settlement are handled entirely by Airwallex.

Airwallex is a PCI DSS Level 1-certified provider, the highest possible tier.


Identity & Authentication

Access to AnkorPay is secured using OAuth 2.0 with PKCE via Kinde, our dedicated Identity Provider. Every API request is validated against a signed JWT token. Tokens expire after 1 hour and are verified on every request. There is no persistent server-side session.

Strong Customer Authentication (SCA)

Sensitive operations (card issuance, fund transfers, payouts) require a second authentication factor via Airwallex's SCA SDK. The challenge must be satisfied before the operation proceeds. SCA tokens are session-scoped and cleared on browser close.


Role-Based Access Control

AnkorPay enforces a six-tier permission model, scoped to each organization. A user's role in one organization is independent of their access in any other.

RoleWhat they can do
OwnerFull organizational access and administration
AdminAll operations across all connected accounts
Vessel AdminAdmin capability limited to their assigned vessels
ApproverApprove transactions and fund transfers
SpenderInitiate transactions on their connected account
ViewerRead-only access

Access to connected accounts is granted explicitly and is not assumed from organization membership.


Multi-Tenancy & Data Isolation

Every record in AnkorPay (transactions, cards, wallets, expense reports, audit logs) is bound to an organization at the database schema level. There is no query path that crosses organization boundaries, regardless of application logic.

For large organizations, vessel-level access control provides an additional layer: administrators can restrict team members to specific vessels, independently of their broader organizational role.


Encryption

DataStandard
In transit (client to platform)TLS 1.3, managed by Cloudflare's global edge
In transit (internal services)Cloudflare private network. Traffic stays within Cloudflare's fabric.
In transit (platform to database)TLS 1.2+, enforced at connection level
At rest (database)AES-256 via hardware module
At rest (audit logs)AES-256, managed by Cloudflare
Secrets & credentialsEncrypted at rest, access-controlled, never in source code

Infrastructure

AnkorPay runs entirely on Cloudflare Workers, a globally distributed, zero-trust edge runtime. Each request executes in an isolated environment with no shared memory between customers or requests.

Internal services are not exposed to the public internet. All external traffic enters through a single API gateway, where authentication and authorization are validated before any business logic executes. DDoS protection is active at the network level across Cloudflare's global infrastructure.


Audit Trail

Every significant action on the platform generates an immutable audit log entry, capturing who did what, when, and on which organization's behalf. Logs cover:

  • All financial operations (transactions, transfers, deposits, conversions)
  • Card and cardholder lifecycle events
  • Organizational changes (invites, role changes, feature configuration)
  • Document operations (expense reports, charters)

Audit logs are organization-scoped. Users can only query their own organization's history.


Observability & Incident Response

All AnkorPay services are instrumented with Sentry for end-to-end distributed tracing. Every request generates a complete trace across the full service chain, from the edge through internal services to the database, giving the engineering team immediate visibility when something goes wrong. Errors are detected and attributed in real time, with full context. 100% of requests are traced across all environments.


Questions?

We're happy to walk through any of the above in detail, provide additional documentation, or arrange a technical call with our engineering team.

Engineering: engineering@ankor.io
Support: support@ankor.io

Airwallex compliance documentation (PCI AOC, SOC 2 Type II reports, penetration test summaries) is available on request via security.airwallex.com.