Integrate PayTrace AI directly into your ERP listeners, payment aggregators, billing pipelines, and dispute resolution workflows. Trigger multi-agent investigations, query topological money trails, and automate reconciliation webhooks with clean REST APIs and native SDKs.
Authenticate all REST requests using Bearer tokens provisioned in your PayTrace Command Center dashboard.
PayTrace provides two distinct key prefixes for development isolation. Keys can be scoped with granular read/write permissions per microservice:
pt_test_... — Sandboxed execution with synthetic banking fixtures and deterministic simulator cases.pt_live_... — Production environment connected to live banking switches, gateway webhooks, and ERP nodes.| HEADER | TYPE | DESCRIPTION |
|---|---|---|
Authorization |
Required | Bearer pt_live_... (Your Secret API Key) |
Content-Type |
Required | application/json (For all POST/PATCH requests) |
X-PayTrace-Tenant |
Optional | Target tenant ID for multi-entity corporate structures |
X-Idempotency-Key |
Recommended | Unique UUID to prevent duplicate execution on network retries |
curl -X POST "https://api.radlabforge.com/v1/investigations" \
-H "Authorization: Bearer pt_test_881902849102ab" \
-H "Content-Type: application/json" \
-H "X-Idempotency-Key: 99a1288b-4712-44df-0019" \
-d '{
"dispute_reference": "DISP-2026-9082",
"claim_type": "MISSING_SETTLEMENT",
"transaction_amount": 842000.00,
"currency": "INR",
"counterparty": {
"name": "ABC Industries",
"identifier": "CUST_ABC_9921"
}
}'
Select any endpoint below, inspect the payload, edit parameters, and click [ SEND REQUEST ] to execute simulated live requests against the PayTrace engine.
Initiate an autonomous multi-agent investigation for a missing payment, dropped settlement, or ledger discrepancy.
Submit transaction claims and let PayTrace AI orchestrate multi-agent reasoning workers to reconstruct the money trail.
/v1/investigations
Initiates an asynchronous multi-agent investigation. Returns an immediate 201 Created with a case_id and streaming webhook listener configuration.
dispute_reference (string, required): External CRM or ERP ticket ID.claim_type (enum, required): MISSING_SETTLEMENT, DUPLICATE_PAYOUT, CHARGEBACK_FRAUD.transaction_amount (float, required): Disputed amount.currency (string, required): 3-letter ISO code (e.g. INR, USD, EUR)./v1/cases/{case_id}
Fetches complete case intelligence, ranked hypotheses with Bayesian likelihood scores, contradictory records resolved, and the cryptographic audit hash.
hypotheses[]: Array of evaluated root cause theories.supporting_evidence[]: Array of verified bank switch & ERP nodes.contradictions[]: Unmatched ledger items explained.immutable_audit_hash: Tamper-evident SHA-256 seal.Upload bank statements, SWIFT MT103 slips, and ERP PDF invoices to cross-reference against transactional nodes.
The Evidence API uses our specialized PT-OCR-Vision-v3 model to extract structural invoice lines, UTR bank codes, and SWIFT stamps with 99.4% cross-validation accuracy against raw bank switch records.
/v1/evidence/verify
// SUBMIT HASH & RECEIPT
{
"case_id": "PT-92881",
"document_type": "BANK_SWITCH_LOG",
"document_sha256": "9f86d081884c7d659a2feaa0c55ad015...",
"expected_fields": { "rrn": "881902849102", "amount": 842000.00 }
}
Query topological graph relations across complex enterprise money flows and multi-hop gateway hops.
Retrieve all upstream and downstream transactional nodes connected to a root transaction or bank switch reference.
Fuzzy cluster matching to identify duplicate vendor accounts, hidden corporate parentage, and synthetic identity rings.
Identify specific gateway timeout edges or settlement clearinghouse nodes causing systematic fund drop-offs.
Receive instant notifications as autonomous agents discover root causes or detect high-risk ledger anomalies.
investigation.completed
HIGH CONFIDENCE
anomaly.detected
EXPOSURE ALERT
evidence.contradiction_resolved
GRAPH RESOLVED
reconciliation.approval_required
DUAL APPROVAL NEEDED
Every webhook request includes an X-PayTrace-Signature header. Verify the cryptographic digest in Node.js:
import crypto from 'crypto';
function verifyWebhook(payload, signature, secret) {
const expected = crypto
.createHmac('sha256', secret)
.update(payload, 'utf8')
.digest('hex');
return crypto.timingSafeEqual(
Buffer.from(signature),
Buffer.from(expected)
);
}
Build faster with native, type-safe SDKs maintained directly by the RadLabs core engineering team.
Async/await support, Pydantic v2 validation, native Pandas integration.
Full TypeScript definitions, Webhook middleware for Express/Next.js.
High-concurrency graph tracing client with native context cancellation.
Enterprise Spring Boot starter with automated connection pooling.
Deterministic error responses with structured machine codes and direct documentation anchors.
| HTTP STATUS | ERROR CODE | REASON / MEANING | REMEDIATION STEP |
|---|---|---|---|
400 Bad Request |
INVALID_PAYLOAD_SYNTAX |
Malformed JSON or missing required fields | Verify request schema against OpenAPI spec |
401 Unauthorized |
INVALID_API_KEY |
Missing or revoked API bearer key | Rotate or generate key in Command Center |
403 Forbidden |
INSUFFICIENT_ROLE_PRIVILEGES |
Key role lacks permission for target endpoint | Adjust RBAC tier in Tenant IAM settings |
409 Conflict |
IDEMPOTENCY_KEY_REPLAY |
Same idempotency key with differing payload | Generate fresh UUID for distinct request |
422 Unprocessable |
EVIDENCE_HASH_MISMATCH |
Provided SHA-256 does not match binary blob | Recalculate SHA-256 before upload |
429 Rate Limited |
RATE_LIMIT_EXCEEDED |
Breached 10,000 req/min enterprise quota | Implement exponential backoff or request upgrade |
Get instantaneous access to our test environment with pre-populated synthetic banking switches, ERP schemas, and live dispute simulation fixtures.