Integrations

Plug into your existing PSP stack.

AVIEL connects via REST API and listens on webhooks. No rerouting. No downtime. Median integration: 3 days.

Connection Methods

Four attachment points — all additive, none invasive

REST API Standard HTTPS endpoints. Authenticated via API key. OpenAPI spec available in docs.

Webhook Listener Register your endpoint. AVIEL pushes structured event payloads in real time.

Open Banking Passthrough Attaches as a signal consumer on PSD2-compliant notification flows.

SMS Gateway Tap Connects to your SMS routing layer. No SIM card. No carrier agreement needed.

{
  "event": "payment.intent.suspicious",
  "timestamp": "2025-09-14T14:32:07Z",
  "customer_id": "cust_8f3a2d...",
  "channel": "sms",
  "aviel_trigger": true,
  "intercept_id": "int_9b4c1e...",
  "risk_score": 0.91,
  "scam_type": "investment_impersonation",
  "honeybot_status": "engaging"
}

Attaches to your notification stack. Touches nothing else.

AVIEL registers as a signal consumer on your existing webhook bus. It does not sit in the payment path, does not require PSD2 passthrough permissions, and does not touch card data or account credentials. The platforms below represent the integration patterns we've validated — if yours isn't listed, ask.

CoreLedger API

PulsePayments

BankBridge SDK

Vertex PSD2 Gateway

NovaPay Rails

SignalBank Core

Go-Live Timeline

Three days from sandbox to live intercepts.

No sprint needed. No infrastructure change. Your engineering team handles this in parallel with other work.

Day 1

API key + sandbox

API key issued. Sandbox environment provisioned. Test intercept fires against a synthetic scammer conversation — verify your ops alert queue receives the payload.

Day 2

Webhook configured

Register your webhook endpoint. Configure on your notification bus. AVIEL's event schema documented at docs/webhook-events. End-to-end test complete.

Day 3

Live on first cohort

Enable live intercept on a low-risk transaction cohort — typically 5–10% of payment intents by volume. First real honeybot engagement typically occurs within 4 hours of go-live. Your fraud ops team reviews the first live scammer profile before end of day.