Meet your stack where it lives.
OneAI plugs into acquirers, PSPs, PayFacs, and aggregators without a rip-and-replace. Six integration layers, dozens of pre-built connectors, and deployment topologies from SaaS to BYOC.
From ingestion to identity — one integration surface.
Every buyer asks about these six things in the same order. Here is what OneAI ships for each.
Data in
REST push, streaming, CDC, batch, and pre-built processor connectors. Same six canonical objects power the whole platform.
- REST —
POST /v1/events/transactions - Streaming — Kafka, Kinesis, PubSub
- CDC — Debezium, Fivetran, Airbyte
- Batch — SFTP, S3 (CSV / Parquet)
Actions out
Signed webhooks, callback APIs, Slack/Teams, ticketing, CRM sync, reverse ETL — OneAI writes back to the systems you already run.
- HMAC-signed webhooks + DLQ
- Slack, Teams, PagerDuty, SMS
- Salesforce / HubSpot / Jira / ServiceNow
- Reverse ETL to Snowflake / BigQuery
Identity & audit
Enterprise SSO, SCIM provisioning, RBAC, and audit log export to any SIEM — non-negotiable for regulated buyers.
- SAML 2.0 + OIDC (Okta, Azure AD, Ping)
- SCIM v2 provisioning
- Fine-grained RBAC + custom roles
- Audit export to Splunk, Datadog, Elastic
Deployment topology
Same code, same UX, different control plane. Multi-tenant SaaS, single-tenant, BYOC, or private VPC.
- SaaS multi-tenant (fastest)
- SaaS single-tenant (regulated PSPs)
- BYOC in your AWS / Azure / GCP
- Private VPC / on-prem for tier-1
Security & compliance
Field-level encryption, BYOK, IP allowlisting, PrivateLink, and a full compliance posture built for procurement teams.
- SOC 2 Type II · PCI DSS · ISO 27001
- GDPR · NDPR · CBN Data Protection
- BYOK / customer-managed keys
- Data residency: EU · US · Africa
Developer experience
OpenAPI 3.1, SDKs in five languages, an interactive sandbox, and a webhook tester that replays any event.
- OpenAPI 3.1 + interactive docs
- SDKs: Node · Python · .NET · Go · Java
- Sandbox seeded with synthetic data
- Webhook replay + rate-limit headers
Skip the build. Ship in weeks, not quarters.
The systems your team already runs — processors, warehouses, identity, ops — all wired up out of the box.
Custom connectors available under Professional and included in Enterprise.
Ship an integration in an afternoon.
Push events with a REST call. Receive signed webhooks. Everything HMAC-signed, idempotent, versioned, and replayable.
1POST /v1/events/transactions HTTP/1.12Host: api.oneai.app3Authorization: Bearer sk_live_9xB...t2Q4Idempotency-Key: 2f0a-7c11-9e33-01ac5Content-Type: application/json67{8 "merchant_id": "mid_4051_8827",9 "aggregator_id": "agg_apay_ng",10 "occurred_at": "2026-08-13T14:22:07Z",11 "type": "auth",12 "amount": { "value": 24999, "currency": "USD" },13 "descriptor": "ACME COFFEE * NG",14 "card": {15 "bin": "455673",16 "last4": "0198",17 "scheme": "visa",18 "country": "NG"19 },20 "device": { "ip": "102.89.3.14", "fingerprint": "df_9k2..." },21 "result": "approved"22}1POST /oneai/webhooks HTTP/1.12Host: hooks.customer.com3X-OneAI-Event: alert.escalated4X-OneAI-Signature: t=1755100927, v1=b6a7...e91d5X-OneAI-Delivery: evt_7f22a1c867{8 "id": "evt_7f22a1c8",9 "type": "alert.escalated",10 "created_at": "2026-08-13T14:22:41Z",11 "data": {12 "merchant_id": "mid_4051_8827",13 "alert_id": "alr_88a2",14 "rule": "chargeback_ratio.7d > 1.0%",15 "severity": "high",16 "evidence": [17 { "kind": "chargeback_ratio", "value": 0.0142, "window": "7d" },18 { "kind": "descriptor_mismatch", "expected": "ACME COFFEE",19 "observed": "ACME * COFFEE-NG" }20 ],21 "rfi": {22 "status": "drafted",23 "template": "chargeback_ratio_v3",24 "sla_hours": 4825 }26 }27}1$ curl https://api.oneai.app/v1/merchants/mid_4051_8827 \2 -H "Authorization: Bearer $ONEAI_API_KEY"34$ npm install @oneai/sdk # Node5$ pip install oneai # Python6$ dotnet add package OneAI # .NET- OpenAPI 3.1 spec + interactive docs
- Idempotency keys on every write
- Cursor pagination + rate-limit headers
- HMAC-signed webhooks with DLQ
- Sandbox with realistic synthetic merchants
- Webhook replay from the console
- SDKs: Node, Python, .NET, Go, Java
- 12-month deprecation windows
Same code. Your control plane.
Pick the topology that matches your regulator, your infosec team, and your timeline.
| Model | Best fit | Time to live | Data resides in | Control plane |
|---|---|---|---|---|
| SaaS multi-tenant | Starter / Professional | Days | OneAI US or EU region | OneAI-managed |
| SaaS single-tenant | Regulated PSPs | 2–4 weeks | Dedicated OneAI cell | OneAI-managed |
| BYOC (your cloud) | Data-residency-sensitive | 4–8 weeks | Your AWS / Azure / GCP | Shared |
| Private VPC / on-prem | Tier-1 banks | Quarter | Your data center | Customer-run |
Built to survive procurement.
The security posture your CISO and your regulator both expect — documented, testable, and portable across topologies.
An 8-step onboarding you can plan around.
Every OneAI rollout follows the same disciplined path — discovery, sandbox, backfill, parallel run, cutover — so you always know where you are.
- 01Discovery & data mappingOne workshop. Six canonical objects. Named integration engineer.
- 02Sandbox provisionedSynthetic merchants, seeded rules, API keys within a day.
- 03Data connectors wiredPick from the connector library or use REST / streaming / CDC.
- 04Rule library importedStart from OneAI defaults, customize with maker-checker.
- 05Historic backfillLast 90 days replayed so alerts have proper baselines.
- 06Parallel runOneAI runs alongside your current tools; compare weekly.
- 07CutoverMaker-checker approves; OneAI becomes system of record.
- 08Ongoing CSMQuarterly business reviews and roadmap alignment.
Book an integration review with an engineer, not a salesperson.
We map your current stack against the six integration layers and hand you a written rollout plan.