ACM Global Tech documentation
Documentation for teams building on ACM
This hub gives engineering, security, and product leaders a public view of how ACM Global Tech's banking platform works, from core concepts to APIs and SDKs. Full API reference, sandbox keys, and integration guides are provisioned to your team in the secure client portal during onboarding.
What the documentation covers
The public overviews below explain how each part of the platform fits together so your team can scope an integration before onboarding. Each area maps to deeper, version-controlled reference material released to clients in the portal.
Getting started
Orientation for your first integration: how environments, authentication, and the onboarding path are structured, and what your team needs before sandbox access is granted.
Start onboarding →Platform concepts
The model behind the ecosystem, accounts, ledgers, parties, payments, FX, cards, and tokenized assets, and how the modules share infrastructure instead of acting as separate vendors.
Explore the platform →APIs & SDKs
A versioned REST API with first-party SDKs for TypeScript, Python, Go, and Rust. Public overviews summarize resources and patterns; the full reference and OpenAPI specs live in the portal.
Request API access →Integration guides
Task-focused walkthroughs for common builds, opening accounts, moving funds across rails, issuing cards, settling cross-border, and tokenizing assets, written for regulated environments.
See solutions →Security & compliance
How the platform is engineered regulated-first, including post-quantum cryptography, key management, and design that supports SOC 2, ISO 27001, and PCI-DSS requirements.
Trust & security →Webhooks & events
The event model for transactions, settlement, and lifecycle changes, with signing, retry, and idempotency patterns so your systems stay in sync without polling.
Get portal access →Release notes
Versioning policy, change logs, deprecation timelines, and migration notes, so your engineers can plan upgrades around a predictable, documented cadence.
In the client portal →Reference & sandbox
The complete endpoint reference, error catalogs, and a sandbox mirroring production. Both are provisioned per institution through the client portal after onboarding.
Client portal →How access works, and what you build with
ACM keeps high-level documentation public so you can evaluate the platform honestly, while gating the sensitive reference material and credentials that belong behind onboarding and the secure client portal.
- Public here: platform concepts, API and SDK overviews, integration patterns, and security posture, enough to scope and plan an integration before you sign.
- In the client portal: the full API reference, OpenAPI specifications, webhook catalogs, and detailed integration guides, provisioned to your team during onboarding.
- Sandbox & keys: isolated sandbox and production environments with scoped, rotatable API keys, issued to named engineers so you can test against your own tenant first.
- SDK languages: first-party SDKs for TypeScript, Python, Go, and Rust, all targeting the same versioned REST API for consistent behavior across your stack.
- Security by design: post-quantum cryptography for long-lived financial records and a regulated-first architecture, detailed on the post-quantum security page.
- Start with the core: most integrations begin at the banking core, then extend to payments, FX, cards, and tokenization as you grow.
Provision your docs and sandbox
Begin onboarding and we will set up your client portal, issue sandbox credentials to your engineers, and walk your team through the reference and integration guides for the modules you are adopting.
Start onboardingFrequently asked questions
Is the full API reference public?
The overviews on this page are public so you can scope a project before signing. The complete API reference, OpenAPI specifications, webhook catalogs, and step-by-step integration guides are provisioned to your team in the secure client portal during onboarding, alongside environment-specific details for your deployment.
How do we get sandbox credentials and API keys?
Sandbox keys are issued to named engineers through the client portal after onboarding begins. Each institution receives isolated sandbox and production environments, scoped credentials, and rotation controls, so you can build and test against your own tenant before going live.
Which SDK languages does ACM support?
ACM publishes first-party SDKs for TypeScript, Python, Go, and Rust, covering core banking, payments, exchange and FX, cards, and tokenization endpoints. Every SDK targets the same versioned REST API, so behavior is consistent regardless of the language your stack uses.
Where are security and compliance details documented?
Security and compliance documentation covers our regulated-first architecture, post-quantum cryptography, key management, and how the platform is designed to support SOC 2, ISO 27001, and PCI-DSS requirements. Control narratives and audit-support materials are shared with your risk and audit teams through the client portal.