Connector Catalog
Each participant connects its existing carrier, TMS, payment processor, ERP, treasury, procurement, accounting, or banking system once. We link available source evidence into transaction context and return it downstream; fields depend on the connected source and configuration.
185 connectors listed — 16 categories — integration method, data output, and data level for each. Interactive view →
Data Levels
L1 Transaction •
L2 Enriched •
L3 Line-item (SKU + commodity code) •
L4 Full Purchase Object (+ GL, confidence, lifecycle)
Freight Audit & EDI
Freight invoices, audit decisions, carrier payments, and standard X12 transaction sets for shipment-level reconciliation.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| Cass Information Systems (FAP) | EDI / webhook | Cass Information Systems Freight Audit & Payment platform — $35B+ in annual freight spend. Captures audited invoice data including Cass audit disposition, exception types, and recovery amounts. | L1 | Registered |
| Loop (Freight Audit & Payment) | EDI / webhook | Loop (loop.com, formerly Control Pay) — AI-powered freight audit & payment platform. Audits carrier invoices against contracted rates, manages exceptions, and processes carrier payment. Ingested events: invoice.created, invoice.approved, invoice.paid, invoice.disputed, payment.released. Webhook delivery via Svix; set LOOP_WEBHOOK_SECRET (whsec_...) to enable signature verification. Pull sync available with LOOP_API_KEY (Bearer token from Loop dashboard). Public developer docs — no partnership required to configure webhooks. Data types: freight invoice, freight audit, carrier payment. | L3 | Registered |
| EDI 204 Motor Carrier Load Tender | EDI / webhook | Parses ANSI X12 EDI 204 (Motor Carrier Load Tender) files. Extracts shipment ID, SCAC, PO/BOL reference numbers, pickup/delivery dates, shipper and consignee details, stop sequences, and equipment type. Creates freight commitment records that link purchase orders to carrier assignments. | L1 | Registered |
| EDI 210 Motor Carrier Invoice | EDI / webhook | Parses ANSI X12 EDI 210 (Motor Carrier Freight Details and Invoice) files. Extracts PRO number, BOL, SCAC, shipper/consignee, line-item charges, billed weight, freight class, and accessorials into structured purchase objects. | L1 | Registered |
| EDI 211 Motor Carrier Bill of Lading | EDI / webhook | Parses ANSI X12 EDI 211 (Motor Carrier Bill of Lading) files. Extracts BOL number, SCAC, PO references, shipper/consignee details, equipment identifier, billed weight, freight class, NMFC code, and charges. The 211 BOL confirms carrier acceptance of goods and cross-references the 204 load tender, 856 ASN, and 210 freight invoice. | L1 | Registered |
| EDI 214 Shipment Status | EDI / webhook | Parses ANSI X12 EDI 214 (Transportation Carrier Shipment Status Message) files. Extracts PRO number, BOL, SCAC, AT7 status code (including D1 Delivered for POD auto-confirmation), current location, and lading exceptions. Use POST /api/v1/freight/ingest/edi214 for full POD auto-confirm against existing purchases. Use POST /api/v1/connectors/ingest/edi214 for status record creation only. | L1 | Registered |
| Lojistic (+PAY Freight Audit & Payment) | EDI / webhook | Lojistic +PAY — multi-modal Freight Audit & Payment platform. Pull connector: Viacle syncs audited carrier invoices from the Lojistic REST API. Auth: API key pair from app.lojistic.com → Profile → API Keys. Covers parcel, LTL, TL, ocean, rail, and air through a single connection — no per-carrier setup required. Invoices arrive already audited with GL codes, approved amounts, and exception dispositions attached. Docs: https://api.lojistic.com Data types: freight invoice, freight audit, carrier payment. | L3 | Registered |
Freight TMS & Visibility
Transportation management and shipment-visibility data joined to freight invoices, deliveries, and payment records.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| McLeod Software TMS | webhook | McLeod Software Transportation Management System — the dominant TMS for trucking carriers. Ingests load invoices, freight charges, accessorials, and delivery confirmations via webhook. | L1 | Registered |
| MercuryGate TMS | webhook | MercuryGate Transportation Management System — leading TMS for 3PLs, brokers, and shippers. Ingests freight invoices, accessorials, charge exceptions, and POD events via webhook. | L1 | Registered |
| Turvo TMS | webhook | Turvo logistics collaboration platform — used by shippers, carriers, and 3PLs. Ingests freight invoices, charges, and delivery confirmations via webhook. | L1 | Registered |
| Trimble Transportation | webhook | Trimble Transportation TMS (TMW Suite, TruckMate) — partner-gated platform. Push-ingest: customers configure a Trimble outbound webhook/export posting settlement data (invoices, approvals, settlements) to Viacle. Works without Trimble's direct participation via the customer-owned outbound export. | L1 | Partner setup |
| SAP Transportation Management | webhook | SAP Transportation Management (SAP TM) — enterprise TMS module of SAP S/4HANA. ENTERPRISE-GATED (SAP BTP partnership): SAP TM customers configure a CPI/PI iFlow that posts Freight Settlement Documents (FSD) as JSON to Viacle for ingest. | L1 | Partner setup |
| Magnus TMS | webhook | Magnus Technologies TMS — PARTNER-GATED push-ingest connector for Magnus TMS customers' outbound settlement webhooks. Requires a partnership agreement (sign up at magnustech.com). Ingests freight invoices, line-haul, fuel surcharge, and accessorial settlement events. | L1 | Partner setup |
| Blue Yonder TMS | webhook | Blue Yonder TMS (formerly JDA) — enterprise Transportation Management System. ENTERPRISE-GATED push-ingest connector for freight payment vouchers posted by customer-configured outbound integrations. Production access requires Blue Yonder developer program approval; the customer-side outbound voucher feed is the activation path. | L1 | Partner setup |
| Alvys TMS | webhook | Alvys freight operating system (TMS) for carriers, brokers, and owner-operators. Featured OTR Solutions TMS integration partner. Public webhook docs at docs.alvys.com — no partner agreement required; customer configures webhooks in their Alvys account. Ingests load lifecycle and invoice events with full freight audit metadata. | L1 | Registered |
| Rose Rocket TMS | webhook | Rose Rocket TMS for carriers, brokers, and 3PLs — strong in NA cross-border. Public OAuth 2.0 + webhook docs at roserocket.readme.io; customer configures OAuth app and webhook subscriptions in their Rose Rocket account. No partner agreement. Ingests order lifecycle and invoice events with full freight audit metadata. | L1 | Registered |
| project44 | webhook | GPS-verified proof-of-delivery signals across 1M+ carrier lanes (LTL, FTL, parcel, ocean, air, rail) via the project44 freight visibility network. | L1 | Registered |
| Flexport | webhook | Freight invoice charges from Flexport international freight forwarding (ocean, air, truck, rail). Pulls itemized charges — linehaul, fuel, port fees, customs, insurance — per shipment invoice. | L1 | Registered |
| Freight Hero / Freight Ops Platform | webhook | FreightHero and compatible freight ops platforms. When a load closes (POD collected, delivery confirmed), POST the operational context — contracted rate, carrier SCAC, delivery timestamp, optional invoice amount — to Viacle. Viacle returns an inline audit result: MATCHED, OVERCHARGE, or PENDING_INVOICE with delta_usd and dispute_ready flag. If invoice_amount is omitted Viacle creates a pending record that reconciles automatically when the carrier invoice arrives via EDI 210, Loop, Cass, or any FAP connector. Events: load.closed | load.delivered | pod.collected. Set FREIGHT_HERO_WEBHOOK_SECRET to enable HMAC-SHA256 signature verification. Data types: freight invoice, freight audit, load close. | L3 | Registered |
| Freight Operations Platform | webhook | Inbound load-close events from freight operations platforms. POST contracted rate, carrier SCAC, delivery/POD details, and an optional invoice amount to receive an inline invoice audit result. Data types: freight invoice, freight audit, load close. | L3 | Registered |
| Shipwell TMS | webhook | Shipwell (shipwell.com) is a mid-market Transportation Management System with a public REST API (docs.shipwell.com). This connector syncs closed and delivered shipment charges from the Shipwell API, capturing shipper charge, carrier charge, and broker markup on each load. It also accepts webhook events (shipment.closed / shipment.delivered) for real-time freight cost capture without waiting for the sync cycle. Auth: Bearer token from app.shipwell.com → Settings → API Tokens. Set SHIPWELL_WEBHOOK_SECRET to enable X-Shipwell-Signature-SHA256 verification. Data types: freight invoice, freight audit, load close. | L3 | Registered |
Freight Carriers
Carrier shipment, invoice, tracking, and proof-of-delivery events from parcel and LTL networks.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| UPS | webhook | UPS parcel carrier — self-serve developer portal (developer.ups.com) with OAuth 2.0. UPS exposes no public invoice pull API; billing data arrives via UPS Billing Center exports pushed to POST /api/v1/connectors/ingest/ups. Normalizes parcel invoices into freight purchase records with per-charge line items and audit metadata. | L1 | Registered |
| FedEx | webhook | FedEx parcel carrier — ingests FedEx Billing Online (FBO) invoice exports pushed to POST /api/v1/connectors/ingest/fedex. Normalizes transportation, fuel surcharge, and accessorial charges into audited purchase records with derived SCAC (FDE / FDEG / FXFE). Self-serve dev portal at developer.fedex.com. | L1 | Registered |
| DHL Express | webhook | DHL Express (MyDHL API) international parcel carrier. Ingests DHL Express billing export data (invoices, AWB-level charges, fuel surcharges, accessorials) via inbound webhook. Covers DHL Express only — DHL Freight is a separate agreement. The MyDHL API exposes no billing pull endpoint, so billing export must be pushed to Viacle. | L1 | Registered |
| TForce Freight | webhook | TForce Freight LTL carrier (former UPS Freight, sold to TFI International in 2021; SCAC TFIN, legacy UPGF on older docs). Ingests carrier invoices with PRO/BOL numbers, NMFC class, billed weight, fuel surcharge, and accessorials for the three-way freight audit engine. Pull sync requires per-customer API enablement via the TForce developer portal; otherwise push invoice data to POST /api/v1/connectors/ingest/tforce_freight. | L1 | Registered |
| Estes Express Lines | webhook | Estes Express Lines LTL carrier (SCAC: EXLA). Self-serve developer portal at developer.estes-express.com — no partner agreement required; API key issued via self-service signup. Ingests LTL freight invoices with PRO/BOL, billed weight, NMFC class, fuel surcharge, and accessorials for the three-way freight audit engine. | L1 | Registered |
| Saia Inc. | webhook | Saia LTL freight carrier (SCAC: SAIA). Self-serve developer portal at api.saia.com — subscription key via self-service signup; no partner agreement required. Ingests LTL freight invoices with PRO/BOL, billed weight, NMFC class, fuel surcharge, and accessorials for the three-way freight audit engine. | L1 | Registered |
| R+L Carriers | webhook | R+L Carriers LTL freight carrier (SCAC: RLCA). Self-serve developer portal at technology.rlcarriers.com — no partner agreement required; full REST API for tracking, rating, BOL, cargo claims, and invoice retrieval. Ingests LTL freight invoices with PRO/BOL, billed weight, NMFC class, fuel surcharge, and accessorials. | L1 | Registered |
| ArcBest / ABF Freight | webhook | ArcBest / ABF Freight LTL carrier (SCAC: ABFS). Self-serve API at arcb.com/technology/shippers/API — account-based setup, no formal partner agreement required. OpenAPI spec published. Ingests LTL freight invoices with PRO/BOL, billed weight, NMFC class, fuel surcharge, and accessorials. | L1 | Registered |
| Old Dominion Freight Line | webhook | Old Dominion Freight Line LTL carrier (SCAC: ODFL, #2 US LTL by revenue). REST API at odfl.com/us/en/resources/shipping-api-integrations — account-based self-service setup, SOAP retired Dec 2025 in favor of REST. Ingests LTL freight invoices with PRO/BOL, billed weight, NMFC class, fuel surcharge, and accessorials. | L1 | Registered |
| Samsara | webhook | Samsara fleet telematics and ELD connector for GPS-verified proof-of-delivery. Public API at developers.samsara.com — OAuth 2.0 self-service app registration; no partner agreement required. Fleet operators authorize Viacle to receive route stop and trip completion events, producing fraud-resistant POD timestamps. | L1 | Registered |
| Motive | webhook | Motive (KeepTruckin) fleet telematics and ELD connector for GPS-verified proof-of-delivery. Public OAuth 2.0 API at developer.gomotive.com — self-service app registration; no partner agreement required. Fleet operators authorize Viacle via OAuth to receive trip completion events, producing fraud-resistant POD timestamps with end-location GPS. | L1 | Registered |
Freight Payments
Lumper, fleet-check, accessorial, and carrier payment events from logistics payment platforms.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| Relay Payments | webhook | Relay Payments digital OTR payment network — 350K+ drivers, 90K+ carriers, 1,600+ truckstops. Captures every fuel, lumper, parking, scale, and roadside expense as a programmable purchase record. | L1 | Registered |
| RoadSync (Logistics Payments) | webhook | RoadSync (roadsync.com) — the logistics-payments platform for trucking. Processes lumper fees, fleet checks (Comcheks/EFS), accessorial charges (detention, layover, fuel surcharge), and vendor payments via ACH and Real-Time Payments. Viacle captures the purchase record — load #, commodity, lumper hours, accessorial code, warehouse ID — that never travels with the payment rail alone. Ingested events: transaction.completed, transaction.refunded. Signature verification via X-RoadSync-Signature (HMAC-SHA256); set ROADSYNC_WEBHOOK_SECRET to enable. Pull sync available with ROADSYNC_API_KEY. Checkout API: https://roadsync.com/checkout-api — no partnership gate. Data types: lumper payment, fleet check, accessorial charge, logistics vendor payment. | L2 | Registered |
Card & Payment Rails
Card, ACH, wallet, crypto, and other payment events normalized into a common transaction and purchase context.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| ISO 20022 / SWIFT / Bank Statement | API pull | Universal banking message connector. Parses ISO 20022 XML (pain.001, pacs.008, camt.052, camt.053, camt.054, remt.001), plus SWIFT MT940/MT942 and BAI2 flat-file formats. camt.035 proprietary-format investigations are ecosystem context only and are not accepted for ingest. Data types: pain.001, pacs.008, camt.052, camt.053, camt.054, remt.001, mt940, mt942, bai2. | L1 | Registered |
| FedNow | API pull | Federal Reserve FedNow Instant Payment Service connector. Parses FedNow JSON message format (based on ISO 20022 pacs.008 semantics) and maps payment notifications into Viacle Purchase Objects with full round-trip traceability. Data types: fednow payment notification, fednow credit transfer. | L2 | Registered |
| SEPA Instant Credit Transfer | API pull | SEPA Instant Credit Transfer (SCT Inst) connector. Parses pacs.008.001.x ISO 20022 XML messages from the SEPA Instant rail (EBA RT1, TIPS) and maps euro-area credit transfers into Viacle Purchase Objects. Data types: sepa instant credit transfer, pacs.008. | L1 | Registered |
| UPI (Unified Payments Interface) | API pull | India's Unified Payments Interface (UPI) connector. Parses UPI payment notification JSON objects from NPCI-compatible sources and maps them to Viacle Purchase Objects, preserving UPI Transaction Reference Numbers for traceability. Data types: upi payment notification, upi collect request. | L2 | Registered |
| Stripe | API pull | Stripe payment connector. Supports checkout sessions (with line items), payment intents (with Level 2/3 Enhanced Scheme Data line items when submitted by the merchant), invoices (subscription & B2B billing with full line items), and direct charges. All three sync paths run concurrently; checkout sessions are preferred for one-time purchases, invoices for recurring/subscription billing. Data types: checkout.session.completed, payment intent.succeeded, payment intent.payment failed, invoice.paid. | L2 | Registered |
| Coinbase Commerce | API pull | Coinbase Commerce connector. Ingests crypto payment charges via webhook (charge:confirmed, charge:resolved) and syncs historical charges via the Commerce API. Supports BTC, ETH, USDC, SOL, and other cryptocurrencies — mapped to local fiat pricing with FX rate capture. Data types: charge:confirmed, charge:resolved, charge:failed. | L1 | Registered |
| Hedera Stablecoin Studio | API pull | Hedera Hashgraph connector via the public Mirror Node REST API. Polls HBAR and HTS (Hedera Token Service) token transfers — including Hedera Stablecoin Studio issued tokens — and ingests them as Viacle Purchase Objects. Supports mainnet, testnet, and previewnet. Data types: hbar transfer, hts token transfer. | L1 | Registered |
| x402 (HTTP 402 Payment Protocol) | API pull | x402 is an open machine-to-machine payment standard built on HTTP 402. Clients attach a cryptographically signed payment authorization (typically USDC on Base or other EVM chains) to API requests. Viacle ingests verified x402 payment proofs as Purchase Objects, creating a canonical data record for every machine payment. Data types: x402 payment proof. | L2 | Registered |
| NACHA ACH File | API pull | Parses NACHA-format ACH files (94-character fixed-width records) into Viacle Purchase Objects. Supports all standard entry class codes (PPD, CCD, CTX, WEB, TEL, POP, ARC, RCK) and ingests both debit and credit entries. Pre-notes and zero-dollar remittance records are skipped. Push-only — send the raw file text to POST /api/v1/connectors/ingest/nacha_ach. Data types: PPD, CCD, CTX, WEB, TEL, POP, ARC, RCK. | L1 | Registered |
| Digital Wallets | API pull | Normalises wallet payment transactions (Apple Pay, Google Pay, Samsung Pay, PayPal, Venmo, Cash App, Amazon Pay, Alipay, WeChat Pay) into Viacle Purchase Objects. Detects card-tokenising wallets (Apple Pay, Google Pay, Samsung Pay) and surfaces the underlying card network. Recognises Mastercard MDES token BINs (540000–549999) and Visa VTS token BINs via inferWalletFromBin(). Push-only — send wallet transaction JSON to POST /api/v1/connectors/ingest/digital_wallets. Data types: apple pay, google pay, samsung pay, paypal, venmo, cash app, amazon pay, alipay, wechat pay. | L1 | Registered |
| Primer | API pull | Primer payment orchestration connector. Ingests payment and refund lifecycle events — including first-class order line items from Client Sessions — via webhook or bulk sync. Handles PAYMENT.STATUS_CHANGED and REFUND.STATUS_CHANGED across all Primer-connected processors (Stripe, Adyen, Braintree, and 50+ more). Data types: PAYMENT.STATUS CHANGED, REFUND.STATUS CHANGED. | L2 | Registered |
| Bead | API pull | Bead crypto and digital-wallet payment processor. Ingests completed payments (Bitcoin Lightning, USDC on Base/Solana/Polygon/Ethereum, PayPal, Venmo, Cash App, Klarna, and more) as purchase objects. Supports real-time webhook ingest and historical sync via the Bead Reporting API. Data types: payments/completed. | L2 | Registered |
| Stables (Stablecoin Payments) | API pull | Stables.money stablecoin payment infrastructure. Ingests Stables webhook events (onramp, offramp, and transfer completions) as Viacle Purchase Objects. Every stablecoin payment becomes a structured, GL-codeable purchase record with entity linkage, on-chain reference ID, and full audit trail. Data types: stablecoin onramp, stablecoin offramp, stablecoin transfer. | L1 | Registered |
| Cybrid (Stablecoin Billpay) | API pull | Cybrid stablecoin payment and FX infrastructure. Ingests Cybrid SubscriptionEvent webhook payloads — trade completions (USDC→USD) and transfer completions (crypto deposits, fiat wire withdrawals) — as Viacle Purchase Objects. Every Cybrid-settled payment becomes a structured, GL-codeable purchase record with on-chain and counterparty references. Data types: stablecoin trade, stablecoin transfer, fiat wire payment. | L2 | Registered |
| Rainforest Pay | API pull | Rainforest Pay payment facilitator connector. Ingests payin and refund lifecycle events via webhook or bulk sync. Turns every Rainforest payin — Card, ACH, Apple Pay — into a structured Viacle purchase record with merchant identity, payment method detail, and full lifecycle state. Supports both sandbox and production environments. Data types: payin.succeeded, payin.authorized, payin.processing, refund.succeeded. | L1 | Registered |
| EBT State Data Feed (SNAP / WIC / TANF) | API pull | Ingests Electronic Benefits Transfer (EBT) transaction data from state agencies operating under a signed USDA FNS Data Sharing Agreement. Transforms SNAP, WIC, and TANF purchase records into Viacle Purchase Objects with fraud-prevention signals including skimming risk scores, off-hours flags, balance-drain detection, and FNS store authorization checks. Requires a live state DSA and EBT processor contract (Conduent, FIS, or Solutran) before data flows. Data types: snap purchase, wic purchase, tanf purchase, ebt balance inquiry. | L1 | Registered |
| PingPong (Cross-Border B2B Payments) | API pull | PingPong Global cross-border payment rail. Syncs completed supplier payment records and ingests real-time webhook events (PAYMENT_COMPLETED, COLLECTION_RECEIVED, REFUND_PROCESSED) as structured Viacle Purchase Objects. Every cross-border payment becomes a GL-codeable, entity-linked purchase record with FX rate, origin/settlement jurisdiction, and full audit trail. Data types: supplier payment, cross border transfer, collection received, refund. | L2 | Registered |
| Thunes Accept (Payment Acceptance) | API pull | Thunes Accept API v1. Ingests charged (completed) cross-border payment orders accepted via Thunes hosted payment pages — B2B and B2C. Webhook uses a secure PING model: Thunes sends a notification, Viacle fetches the full transaction detail in real-time. Every charged payment order becomes a structured purchase object with FX metadata, settlement currency, and buyer billing details. Data types: payment order, cross border acceptance, refund. | L3 | Registered |
| Thunes Money Transfer (Cross-Border Payout) | API pull | Thunes Money Transfer API v2. Syncs completed cross-border payout transactions across Mobile Wallet, Bank Account, Cards, and Cash Pickup corridors. Every confirmed payout becomes a structured Viacle purchase object with full FX metadata, sender/beneficiary identity, corridor jurisdiction, and payer network details — ready for GL coding, expense tracking, and 1099 reporting. Data types: cross border payout, mobile wallet transfer, bank transfer, cash pickup. | L1 | Registered |
| Adyen (Payment Platform) | API pull | Adyen global payment platform. Ingests AUTHORISATION, CAPTURE, REFUND, CHARGEBACK, and CANCELLATION events via HMAC-signed webhook notifications. Every settled payment becomes a structured Viacle purchase object with payment method, shopper reference, merchant account, and FX metadata — ready for GL coding, chargeback tracking, and reconciliation. Data types: authorisation, capture, refund, chargeback, cancellation. | L1 | Registered |
| Mollie (European Payment Gateway) | API pull | Mollie payment gateway. Supports real-time webhook ingestion (PING model — Mollie sends a payment ID, Viacle fetches the full payment record) and paginated historical sync. Every paid payment becomes a structured Viacle purchase object with payment method, locale, customer details, and Mollie order metadata. Ideal for European e-commerce and SaaS platforms. Data types: payment, refund, order. | L3 | Registered |
| Rapyd (Fintech-as-a-Service) | API pull | Rapyd Fintech-as-a-Service platform. Ingests PAYMENT_COMPLETED, PAYOUT_COMPLETED, and REFUND_COMPLETED webhook events and syncs historical payments via the Rapyd Collect API. Covers 900+ local payment methods across 100+ countries. Every completed payment becomes a structured Viacle purchase object with payment method type, FX metadata, customer reference, and merchant reference. Data types: payment, payout, refund. | L2 | Registered |
| PayPal | API pull | First-class PayPal connector. Syncs transactions via the Transaction Search API (up to 90-day window per call; full 3-year history available) and paid invoices via the Invoicing API. Webhook ingestion supports PAYMENT.CAPTURE.COMPLETED, PAYMENT.SALE.COMPLETED, CHECKOUT.ORDER.COMPLETED, INVOICING.INVOICE.PAID, BILLING.SUBSCRIPTION.ACTIVATED, and related events with cert-based signature verification via PayPal's /v1/notifications/verify-webhook-signature endpoint. Set PAYPAL_WEBHOOK_ID to enable signature verification on inbound webhooks. Data types: PAYMENT.CAPTURE.COMPLETED, PAYMENT.SALE.COMPLETED, CHECKOUT.ORDER.COMPLETED, INVOICING.INVOICE.PAID, BILLING.SUBSCRIPTION.ACTIVATED, transaction search. | L2 | Registered |
| Dodo Payments | API pull | First-class Dodo Payments connector for SaaS, AI, and digital product billing. Syncs completed payments and active subscriptions via pull. Webhook ingestion supports payment.succeeded, payment.failed, subscription.active, subscription.renewed, subscription.cancelled, and refund.succeeded events. Signature verification uses Standard Webhooks HMAC-SHA256 (webhook-id + webhook-timestamp + body). Set DODO_WEBHOOK_SECRET to enable verification. Data types: payment.succeeded, payment.failed, subscription.active, subscription.renewed, subscription.cancelled, refund.succeeded. | L2 | Registered |
| Airwallex | API pull | First-class Airwallex connector for global cross-border payment infrastructure. Syncs Billing Transactions and paid Invoices via pull. Webhook ingestion supports PAYMENT_ATTEMPT.SUCCEEDED/FAILED, BILLING.INVOICE.PAID/VOIDED, BILLING.SUBSCRIPTION.CREATED/CANCELLED, and BILLING.TRANSACTION.SUCCEEDED. Auth: Client ID + API key → POST /authentication/login token (cached per key:env, refreshed 60s before expiry). Set AIRWALLEX_WEBHOOK_SECRET to enable HMAC-SHA256 signature verification. Data types: PAYMENT ATTEMPT.SUCCEEDED, BILLING.INVOICE.PAID, BILLING.TRANSACTION.SUCCEEDED, BILLING.SUBSCRIPTION.CREATED, billing transactions, invoices. | L2 | Registered |
| Straddle A2A Payments | API / parse | Straddle is a unified account-to-account payment platform running across ACH, RTP, and FedNow rails with built-in KYC, open banking identity, and real-time fraud detection via Watchtower. Ingests settled Straddle charges and payouts as Viacle Purchase Objects. Supports both polling sync and webhook-driven ingestion on charge.settled and payout.settled events. Data types: a2a charge, a2a payout, payment event. | L2 | Registered |
| Brankas Open Finance (SEA) | API / parse | Brankas provides open banking and open finance infrastructure across Southeast Asia — Indonesia, Philippines, Thailand, and Vietnam. Covers Direct (money-in bank transfers), Disburse (money-out), and the Open Finance Suite with account data. Ingests inbound Direct payments as Viacle Purchase Objects with payer identity, amount, bank reference, and settlement metadata. Data types: bank transfer inbound, disbursal, account data. | L2 | Registered |
| Token.io Open Banking Payments (EU/UK) | API / parse | Token.io is a PSD2-licensed open banking platform covering 3,000+ European and UK banks. Supports Single Immediate Payments (SIP), Variable Recurring Payments (VRP), and Account Information Services (AIS). Ingests completed Token.io payment transfers as Viacle Purchase Objects via webhook. Covers UK, EU, and global markets via the Token.io TPP API. Data types: sip payment, vrp payment, ais transaction. | L2 | Registered |
| Aeropay Bank Transfers | API / parse | Aeropay facilitates smart bank transfers and direct bank connections for merchants in cannabis, gaming, healthcare, and other industries that rely on ACH-based payment flows. Ingests settled Aeropay transactions as Viacle Purchase Objects with payer info, amount, merchant, and settlement metadata. Data types: bank transfer, ach transaction. | L2 | Registered |
| Finzly Payment Galaxy (FedNow · ACH · RTP · SWIFT) | API / parse | Finzly's Payment Galaxy is a bank-run unified payment orchestration API covering every major US payment rail — FedNow, ACH, RTP (real-time payments), SWIFT, and Fedwire — plus FX. A single Finzly integration replaces the need to connect individually to each rail. Used by community banks and credit unions. Ingests settled payment transactions as Viacle Purchase Objects with full rail metadata (rail type, direction, counterparty names, and settlement timestamps). Data types: fednow payment, ach payment, rtp payment, swift payment, wire payment. | L2 | Registered |
| Corpay Cross-Border | API pull | Corpay Cross-Border payment rail (NYSE: CPAY). Converts SWIFT/SEPA international supplier payments into structured Viacle Purchase Objects with FX rate, origin/settlement jurisdiction, beneficiary identity, and Payments GPS tracker ID (iso20022_ref). Supports push (webhook: payment.settled/completed) and pull (Lookup Orders API). Auth: 2-token flow — Partner-level token → Client-level token per clientCode. Set CORPAY_CROSSBORDER_WEBHOOK_SECRET to enable HMAC-SHA256 signature verification. Contact TechnicalSales@Corpay.com for credentials. Developer portal: developer.crossborder.corpay.com. Data types: cross border payment, payment.settled, payment.completed, fx payment, supplier payment. | L2 | Registered |
| Pix (Brazil) | API / parse | Ingests Brazil's Pix instant payment rail. Operated by Banco Central do Brasil, Pix is a real-time 24/7 payment system with 140M+ active users. Webhooks follow the BCB Open Finance standard (PIX-API v2.2) and are delivered by PSPs (banks, fintechs) when payments settle. Captures endToEndId, payer CNPJ/CPF, merchant Pix key, and free-text payment description (infoPagador). Pair with the NFe connector for full itemized purchase data on the same transaction. Data types: payments, sender identity, receiver identity. | L2 | Registered |
| Mercado Pago | API / parse | Latin America's dominant payment processor (Mercado Libre / MeLi). 100M+ active users across Brazil, Mexico, Argentina, Colombia, Chile, and Peru. Webhooks deliver an IPN notification; Viacle fetches full payment detail including line items from additional_info.items. Supports credit/debit cards, Pix, boleto, and account money. Pull sync: GET /v1/payments/search?status=approved. Auth: OAuth access_token. Data types: payments, line items, buyer identity, refunds. | L3 | Registered |
| Checkout.com | API / parse | One of the world's largest PSPs by volume. Strong in MENA, UK/EU, and Southeast Asia. Ingests payment_approved, payment_captured, and payment_paid webhook events. Supports Level 2/3 line-item data via items[] on the payment object. Webhook signature: HMAC-SHA256 over raw body via Cko-Signature header. Pull sync: GET /payments (filtered by Captured/Authorized status). Auth: Bearer secret_key (NAS flow). Sandbox: api.sandbox.checkout.com. Data types: payments, line items, refunds, disputes. | L3 | Registered |
| Klarna | API / parse | Leading BNPL (Buy Now Pay Later) provider with 150M+ consumers across 45+ markets. Strategically important: Klarna underwrites by item, so order_lines are always present and include product_identifiers (brand, category_path, color, size, GTIN). Ingests CAPTURE_CREATED and ORDER_STATUS_CHANGED events. Webhook signature: HMAC-SHA256 via Klarna-Signature header. Pull: GET /ordermanagement/v1/orders?status=CAPTURED. Auth: Basic (API key + secret). Data types: payments, line items, product identifiers, buyer identity, refunds. | L3 | Registered |
| Stone (Brazil) | API / parse | Ingests payment events from Stone, Brazil's fastest-growing payment acquirer and fintech platform (STNE). Serves 4M+ SMB merchants across Brazil. Captures card payments, Pix, and boleto settlements via HMAC-signed webhook notifications. Every settled payment becomes a structured Viacle purchase object with customer identity, payment method, and merchant metadata. Data types: payments, customer identity, payment method. | L2 | Registered |
| PagSeguro / PagBank (Brazil) | API / parse | Ingests payment events from PagSeguro (now PagBank), one of Brazil's largest consumer PSPs with 30M+ accounts. Captures credit card, debit card, Pix, and boleto payments via v4 webhook notifications. Every paid charge becomes a structured Viacle purchase object with customer identity, payment method, and line items (when present). Data types: payments, customer identity, payment method, line items. | L3 | Registered |
| Boleto Bancário via Pagar.me | API / parse | Ingests Boleto Bancário payments via Pagar.me (Stone's fintech platform). Boleto is Brazil's bank-slip payment method — a Central Bank-standardized instrument widely used in B2B, subscriptions, and e-commerce. Captures boleto settlements (charge.paid), card payments, and Pix via Pagar.me's HMAC-signed webhook notifications. Compatible aggregators include Pagar.me, Iugu, Asaas, and Efí Bank using similar event shapes. Data types: payments, boleto, customer identity, line items. | L3 | Registered |
| xMoney Crypto (Europe) | API / parse | Ingests crypto payments via xMoney's Crypto API — a MiCA-compliant European crypto payment rail covering all of Europe except France and Kosovo. Accepts BTC, ETH, SOL, EGLD, USDT, USDC, and 30+ more via Binance Pay integration. Merchants settle in EUR, USD, or USDC regardless of the crypto the buyer used. HMAC-SHA256 webhook signatures use alphabetically-sorted, flattened key-value encoding (unique to xMoney). Retry schedule: Fibonacci backoff, 16 attempts over ~16.5 hours. Data types: crypto payments, settlement currency, blockchain metadata. | L2 | Registered |
| EBizCharge | API / parse | EBizCharge by Century Business Solutions — the leading B2B integrated payment processor embedded natively within 100+ ERPs and CRMs (SAP Business One, QuickBooks, NetSuite, Microsoft Dynamics, Salesforce, Epicor, and more). 20,000+ business customers. Ingests commercial card transactions with Level 2/3 data including line items, PO numbers, invoice numbers, commodity codes, and GL details via the EBizCharge Connect SOAP API. Also accepts real-time postbacks from hosted payment forms at POST /api/v1/connectors/ingest/ebizcharge. Data types: line items, invoice number, po number, order id, commodity code, level2 data, level3 data, tax breakdown, card type, auth code, gl description, clerk id. | L3 | Registered |
| NMI | API / parse | Network Merchants Inc. — embedded payments platform powering thousands of ISOs, ISVs, and PayFacs. Acquired Dwolla (ACH/real-time payments) and Fee Navigator (AI interchange pricing). One NMI integration reaches the entire downstream reseller network. Ingests sale and capture webhook events (condition: pendingsettlement or complete). Webhook signature: HMAC-SHA256 via Webhook-Signature header (format: t=nonce,s=hmac). Pull sync: NMI Query API (GET report_type=transaction). Docs: https://docs.nmi.com Data types: payments, captures, refunds, chargebacks. | L2 | Registered |
| Paystand | API / parse | B2B zero-fee payment network (ACH, bank transfer, card) deeply integrated with NetSuite, Sage, BigCommerce, and other ERPs. Covers the ACH/bank-transfer rail gap that card-enrichment providers cannot see. Ingests payment.completed and payment.settled webhook events. Webhook verification: Paystand recommends fetching the event by ID from GET /events/{id} using OAuth2. Pull sync: GET /payments filtered by status=completed. Auth: OAuth2 client_credentials (client_id + client_secret). Docs: https://developers.paystand.com Data types: payments, refunds, disputes. | L2 | Registered |
| Authorize.net | API / parse | Authorize.net (a Visa solution) — one of the largest North American payment gateways, processing for millions of merchants. Webhook events carry a transaction ID; line items fetched via getTransactionDetailsRequest (up to 30 line items per transaction). Ingests authcapture.created and capture.created events. Webhook signature: HMAC-SHA512 via X-ANET-Signature header (format: sha512=UPPERCASE_HEX). Pull sync: getSettledBatchListRequest → getTransactionListRequest → getTransactionDetailsRequest. Docs: https://developer.authorize.net/api/reference/features/webhooks.html Data types: payments, captures, line items, refunds. | L3 | Registered |
| Sila Money | API / parse | Ingests ACH, RTP, and FedNow payment events from Sila Money — a US banking-as-a-service and payments API platform. Captures transfers, disbursements, and digital wallet moves via webhook notifications. Every completed transaction becomes a structured Viacle purchase object with settlement rail, merchant, and jurisdiction metadata. Data types: payments, ach transfers, rtp payments, fednow payments. | L2 | Registered |
| BrasilPays | API / parse | Ingests payment events from BrasilPays — a Brazilian payments platform covering PIX (Brazil's instant payment network), boleto bancário, and card payments. Captures merchant settlements and consumer payments via HMAC-signed webhook notifications. Every completed transaction becomes a structured Viacle purchase object with CNPJ merchant identity, payment rail, and BRL amount data. Data types: payments, pix payments, boleto payments, merchant identity. | L2 | Registered |
| Derivative Path | API / parse | Ingests derivatives settlement and payment events from Derivative Path — a derivatives technology and advisory platform managing ~$500B notional across interest rate, FX, and commodity hedging for banks, credit unions, investment managers, and corporations. Every cash settlement (coupon, premium, FX delivery, collateral call) becomes a structured Viacle purchase object with counterparty identity, asset class, instrument type, and trade reference. Data types: derivative settlements, fx payments, commodity settlements, counterparty identity. | L3 | Registered |
| OFX | API / parse | Ingests international FX transfers and payments from OFX — a global payments platform serving businesses across 170+ countries with competitive exchange rates and no hidden fees. Every completed transfer (DELIVERED / SETTLED status) becomes a structured Viacle purchase object with beneficiary identity, FX rate, source and destination currencies, and payment reference. Rail auto-detected: SWIFT (international / cross-currency), Wire (domestic USD), or ACH. Optional pull sync via OFX_API_KEY. Data types: international transfers, fx payments, beneficiary identity, exchange rates. | L2 | Registered |
| MoonPay | API pull | MoonPay fiat↔crypto on/off-ramp infrastructure. Ingests completed on-ramp and off-ramp transactions via MoonPay webhook events (transaction_created, transaction_updated with status=completed). Every settled MoonPay payment becomes a structured Viacle Purchase Object with fiat amount, crypto asset, wallet address, FX rate, and network fee capture. Used by 500+ partners including MetaMask, Phantom, Exodus, Uniswap, and Mastercard. Data types: transaction created, transaction updated. | L2 | Registered |
| WEX Fleet Card | webhook | WEX fleet card TransConnect API — 550K+ commercial vehicles, $22B+ annual volume. Captures every fueling event with OPIS commodity codes, vehicle/driver identity, odometer, gallons dispensed, and unit price. No merchant partnership required; data flows directly from WEX card-issuer telemetry. Requires WEX Integration Partner agreement (developer.wexinc.com). | L1 | Registered |
| Fleetcor / Comdata Fleet Card | webhook | Fleetcor fleet card network (Comdata, Fuelman, Corpay One) — 700K+ commercial vehicles, $35B+ annual volume. Captures every fueling and fleet expense event with NACS commodity codes, vehicle/driver identity, odometer, quantity dispensed, and unit price. No merchant partnership required; data flows directly from Fleetcor card-issuer telemetry. Requires Fleetcor Integration Partner agreement (developer.fleetcor.com). | L1 | Registered |
| Cybersource | API pull | Pulls card transactions from Cybersource (Visa) Transaction Search with Level 3 line items — product SKU, name, quantity, unit price, and per-line tax — using merchant-owned REST API keys. No partnership required; sandbox keys work at apitest.cybersource.com. Data types: card transactions, level3 line items. | L3 | Registered |
E-Invoice & Tax Mandates
Structured electronic invoices and tax-authority formats. These sources preserve vendor, tax, payment, and line-item fields at origin.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| PEPPOL / UBL e-Invoice | parse | Parses PEPPOL BIS Billing 3.0 and generic UBL 2.1/2.3 e-invoice XML documents into Viacle Purchase Objects. Supports inbound ingestion via POST /api/v1/connectors/ingest/peppol/inbound and legacy POST /api/v1/connectors/ingest/peppol_ubl. Extracts supplier, buyer, invoice lines with GTIN and UNSPSC commodity codes, monetary totals, and VAT amounts. Data types: UBL 2.1 Invoice, UBL 2.3 Invoice, PEPPOL BIS 3.0, CreditNote. | L4 | Registered |
| X12 EDI (810 / 850 / 855 / 856) | parse | Parses ANSI X12 Electronic Data Interchange transaction sets into Viacle Purchase Objects. Supports 810 (Invoice), 850 (Purchase Order), 855 (PO Acknowledgment), and 856 (Advance Ship Notice) with full line-item extraction including GTIN, UPC, SKU, UNSPSC commodity codes, carrier SCAC, and pack hierarchy. Handles standard ISA/GS/ST envelope. Push-only — send raw X12 EDI text to POST /api/v1/connectors/ingest/x12_edi. Data types: 810 Invoice, 850 Purchase Order, 855 PO Acknowledgment, 856 Advance Ship Notice. | L2 | Registered |
| Italy FatturaPA / SdI | parse | Parses Italy's mandatory FatturaPA e-invoice format (SdI clearance model). Mandatory for all domestic B2B/B2G transactions since January 2019. Extracts supplier/buyer party details (Partita IVA), line items with descriptions, quantities, unit prices, and VAT breakdown. Inbound only — push cleared XML from your SdI intermediary. Data types: FatturaPA XML, TD01 Invoice, TD04 Credit Note, TD05 Debit Note. | L2 | Registered |
| India GST E-Invoice (IRP / IRN) | parse | Parses India's GST e-invoice JSON format as issued by the Invoice Registration Portal (IRP). Mandatory for B2B invoices above ₹5 crore turnover threshold (current; expected to drop further). Extracts seller/buyer GSTIN, HSN-coded line items, IGST/CGST/SGST breakdown, IRN, and acknowledgement number. Inbound only — POST the IRP response or e-invoice JSON to the ingest endpoint. Data types: GST E Invoice JSON, IRP IRN Payload, India GST Invoice. | L2 | Registered |
| Saudi Arabia ZATCA Fatoorah | parse | Parses Saudi Arabia's ZATCA Fatoorah e-invoice format (UBL 2.1 XML with ZATCA extensions). Supports both clearance mode (B2B/B2G invoices approved by ZATCA before delivery) and reporting mode (B2C simplified invoices). Mandatory and rolling out by revenue wave through 2026. Extracts seller/buyer VAT registration numbers, line items, SAR amounts, and VAT totals. Inbound only — forward cleared XML from your ZATCA-integrated ERP or middleware. Data types: ZATCA UBL 2.1 XML, Fatoorah Standard Invoice (388), Fatoorah Credit Note (381), Fatoorah Debit Note (383). | L2 | Registered |
| Germany XRechnung | parse | Parses Germany's XRechnung e-invoice format (EN16931 / UBL 2.1 profile). Mandatory for B2G invoices since Nov 2020; B2B receive mandate active from Jan 2025; B2B issue mandate from Jan 2027 (large) / Jan 2028 (all). Extracts BuyerReference (Leitweg-ID), supplier/buyer details, line items, and German VAT amounts. Inbound only — push XRechnung XML from your ERP or ZRE/OZG-RE routing platform. Data types: XRechnung 3.0 UBL, XRechnung 2.x UBL, EN16931 Invoice (DE), UBL 2.1 Invoice (DE). | L4 | Registered |
| France Factur-X / ZUGFeRD | parse | Parses France's Factur-X e-invoice format (identical to ZUGFeRD 2.x used in Germany/Austria). Uses UN/CEFACT Cross-Industry Invoice (CII) XML — distinct from UBL. France B2B mandate rolling from Sep 2026 (ETI/GE) through Sep 2027 (TPE). Supports BASIC, EN 16931 (Comfort), and EXTENDED profiles with line items. Inbound only — POST the extracted CII XML (not the PDF wrapper) to the ingest endpoint. Data types: Factur X EN 16931 (Comfort), Factur X EXTENDED, Factur X BASIC, ZUGFeRD 2.x CII, CII CrossIndustryInvoice. | L2 | Registered |
| Poland KSeF E-Invoice | parse | Parses Poland's KSeF (Krajowy System e-Faktur) mandatory e-invoice XML format (FA_VAT v2 schema). Mandatory for all VAT-registered taxpayers from Feb 1, 2026 (government clearance model). Extracts seller/buyer NIP, PKWIU/CN commodity codes per line item, Polish VAT rate codes (23/8/5/0/zw/np/oo), and KSeF reference number. Inbound only — POST cleared KSeF XML from your ERP or KSeF API integration. Data types: KSeF FA VAT v2 XML, KSeF VAT Invoice, KSeF KOR Correction, KSeF ZAL Advance Invoice. | L2 | Registered |
| Turkey e-Fatura / e-Arşiv (GIB) | parse | Parses Turkey's e-Fatura and e-Arşiv electronic invoice formats (UBL-TR / UBL 2.1 with GIB extensions). Administered by the GIB (Revenue Administration) via the EDAP clearance platform. e-Fatura mandatory since July 2020 for B2B taxpayers above TRY threshold; e-Arşiv mandatory for B2C and unregistered-buyer invoices. Extracts VKN/TCKN (Turkish corporate/individual tax IDs), KDV (VAT) breakdown, line items, and ETTN invoice UUID. Supports SATIS (sale), IADE (return/credit), TEVKIFAT (withholding), and EARSIVFATURA (e-Arşiv) document types. Inbound only — POST GIB-cleared UBL-TR XML from your ERP or EDAP integration. Data types: e Fatura UBL TR XML, e Arşiv UBL TR XML, TEMELFATURA (Basic Invoice), TICARIFATURA (Commercial Invoice), EARSIVFATURA (Archive Invoice), IADE (Return/Credit Invoice), TEVKIFAT (Partial KDV Withholding Invoice), ISTISNA (VAT Exempt Invoice). | L2 | Registered |
| Brazil NFe / NFS-e | parse | Ingests Brazil's government-mandated electronic invoices (Nota Fiscal Eletrônica for goods, Nota Fiscal de Serviços Eletrônica for services). Every commercial transaction in Brazil generates a SEFAZ-issued XML with line items, NCM/CFOP tax codes, ICMS/PIS/COFINS taxes, and CNPJ identifiers for both merchant and buyer. Push: POST raw NFe/NFS-e XML. Pull: SEFAZ NFe Distribuição API (requires e-CNPJ digital certificate). Data types: invoices, line items, tax data, supplier identity. | L3 | Registered |
| Spain SII (AEAT) | parse | Parses Spain's SII (Suministro Inmediato de Información) e-invoice XML submitted to the AEAT (Spanish Tax Agency). Mandatory for VAT-registered businesses above threshold since July 2017. Extracts seller/buyer NIF (Spanish tax ID), IVA breakdown per rate, invoice totals, and operation type. Accepts both Libros de Facturas Emitidas (issued) and Facturas Recibidas (received) formats. Inbound only — push SII XML from your ERP or SII integration middleware. Data types: SII XML, Factura Emitida, Factura Recibida, Factura Rectificativa. | L1 | Registered |
| Mexico CFDI 4.0 (SAT) | parse | Parses Mexico's CFDI 4.0 (Comprobante Fiscal Digital por Internet) e-invoice XML cleared through the SAT (Servicio de Administración Tributaria). CFDI 4.0 mandatory since January 2022. Extracts Emisor/Receptor RFC (tax IDs), Concepto line items with SAT ClaveProdServ commodity codes, IVA tax breakdown, and the fiscal UUID (folio fiscal) from the TimbreFiscalDigital seal. Inbound only — push PAC-cleared CFDI XML from your ERP or SAT integration. Data types: CFDI 4.0 XML, Ingreso (Invoice), Egreso (Credit Note), TimbreFiscalDigital. | L2 | Registered |
| Malaysia MyInvois (LHDN / IRBM) | parse | Parses Malaysian LHDN MyInvois e-invoices into Viacle Purchase Objects. Accepts UBL-JSON (LHDN API format) and PEPPOL PINT-MY UBL XML. Extracts TIN, BRN, MSIC codes, and SST/Service Tax line-item breakdown. Mandatory for taxpayers above MYR 25M revenue from January 2025. Data types: MyInvois UBL JSON, PEPPOL PINT MY UBL XML, MyInvois Credit Note, MyInvois Debit Note. | L1 | Registered |
| Singapore PINT-SG e-Invoice (PEPPOL) | parse | Parses Singapore PINT-SG PEPPOL e-invoices into Viacle Purchase Objects. Accepts PEPPOL PINT-SG UBL 2.1 XML (BIS Billing 3.0 regional profile). Extracts UEN (ACRA company number), GST registration number (IRAS), GST breakdown by tax category (S/Z/E/O), and line items with UNSPSC codes. Mandatory for Singapore public-sector e-invoicing from 2025. Data types: PINT SG UBL 2.1 Invoice, PINT SG UBL 2.1 Credit Note, PEPPOL BIS Billing 3.0 (SG profile). | L2 | Registered |
Document Intelligence & OCR
Receipt, invoice, email, and document extraction. OCR and LLM-assisted records retain the source fields needed to build a purchase object.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| PaddleOCR | API | High-performance OCR engine for extracting text from receipt and invoice images. Supports 80+ languages with multi-directional text detection. Data types: receipt images, invoice images, document scans. | L2 | Registered |
| docTR | API | Deep learning document text recognition by Mindee. Extracts structured text from receipts, invoices, and purchase documents with high accuracy. Data types: receipt images, invoice images, document scans, pdf documents. | L2 | Registered |
| Apache Tika | API | Content detection and text extraction framework. Processes over 1,000 document types including PDFs, emails, and Office documents for purchase data extraction. Data types: pdf documents, email attachments, office documents, receipt images. | L2 | Registered |
| Tesseract OCR | API | Industry-standard open-source OCR engine maintained by Google. Extracts text from receipt images, scanned invoices, and purchase documents. Supports 100+ languages. Data types: receipt images, invoice images, document scans, pdf documents. | L2 | Registered |
| Apache James | email parse | Open-source enterprise mail server. Connects to James mailboxes via REST API to extract and process purchase confirmation emails, order receipts, and invoice notifications. Data types: purchase emails, order confirmations, invoice notifications, shipping updates. | L3 | Registered |
| LlamaOCR | API | LLM-powered OCR engine that uses vision language models to extract structured data from receipt images and documents with high accuracy. Ideal for complex or non-standard receipt formats. Data types: receipt images, invoice images, document scans, handwritten receipts. | L2 | Registered |
| Gmail Receipts | email parse | Scans a Gmail inbox for order confirmation and receipt emails and extracts structured purchase data. Parses schema.org/Order markup embedded by major retailers, with HTML pattern matching as a fallback. Requires a Gmail OAuth access token with gmail.readonly scope. Data types: email confirmation, order receipt. | L3 | Registered |
| Outlook / Microsoft 365 Receipts | email parse | Scans a Microsoft 365 Outlook inbox for order confirmation and receipt emails and extracts structured purchase data. Parses schema.org/Order markup embedded by major retailers, with HTML pattern matching as a fallback. Requires a Microsoft Graph OAuth access token with Mail.Read scope. Data types: email confirmation, order receipt. | L3 | Registered |
| Veryfi | API | Enterprise receipt and invoice OCR API. Extracts Level 3 line-item data — product names, quantities, prices, taxes, and vendor detail — across 91 currencies and 38 languages. Pre-trained on hundreds of millions of receipts with SOC 2 Type II compliance. Supports full sync of all previously-processed documents via GET /documents. Data types: receipt images, invoice images, pdf documents, level 3 line items. | L3 | Registered |
| Sensibill | API | Receipt extraction API purpose-built for financial institutions. Extracts 150+ data points including SKU-level line items, merchant detail, taxes, and totals using multi-brain OCR and self-learning ML. Deployed by banks and credit unions for enriched transaction experiences. Data types: receipt images, sku line items, merchant detail, tax data. | L3 | Registered |
| Amazon Textract | API | AWS managed document intelligence service. Extracts text, forms, tables, and line items from receipts and invoices using ML models trained by AWS. Supports QUERIES mode for targeted field extraction and EXPENSE_ANALYSIS for receipt-specific structured output. Data types: receipt images, invoice images, pdf documents, expense analysis. | L2 | Registered |
Bank Feeds & Open Finance
Bank transaction and remittance feeds that supply payment-side context for ACH, wire, and account-based purchases.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| TrueLayer Open Banking | API pull | TrueLayer connects to 3,000+ banks across the UK and Europe via FCA-regulated open banking rails (UK FCA AIS, EU PSD2). Businesses authenticate once via OAuth; all subsequent transactions arrive as webhooks and are converted to Viacle Purchase Objects automatically. First bank-feed connector: bank feed is the trigger, no receipt upload needed. Data types: bank transaction, transaction created, transaction settled, account. | L2 | Registered |
| CheckAlt ClearingWorks | API pull | Lockbox + integrated receivables: captures check, ACH, card, and RDC payment remittance data from the ClearingWorks platform. Provides invoice references and applied amounts for AR-side reconciliation. | L1 | Registered |
Financial Systems
Financial account, transaction, invoice, and payment data from systems that already record business spend.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| Firefly III | API pull | Personal finance manager. Syncs withdrawal transactions as purchase objects. Each transaction produces a single synthetic line item from the transaction description and amount — no product-level line items. Best paired with receipt ingestion for item-level completeness. Data types: transactions, categories, budgets, accounts. | L2 | Registered |
| Akaunting | API pull | Online accounting software for small businesses. Syncs invoices, bills, and payment transactions as purchase objects with full line-item detail. Data types: invoices, bills, payments, vendors. | L2 | Registered |
| Invoice Ninja | API pull | Open-source invoicing and billing platform. Connects via REST API to sync invoices, payments, expense records, and vendor data for purchase object creation. Data types: invoices, payments, expenses, vendor records. | L2 | Registered |
| InvoicePlane | API pull | Self-hosted open-source invoicing application. Connects via REST API to sync invoices, invoice items, payment records, and client data for purchase tracking. Data types: invoices, invoice items, payments, client records. | L3 | Registered |
| Open Accounting | API pull | Open-source double-entry accounting platform. Connects via REST API to sync transactions, journal entries, invoices, and account data for purchase object creation. Data types: transactions, journal entries, invoices, account records. | L2 | Registered |
| Kill Bill | API pull | Open-source subscription billing and payments platform. Connects via REST API to sync invoices, invoice items, and payment records across accounts. Data types: invoices, invoice items, payments, accounts. | L3 | Registered |
| MX Platform (Bank Feed + Recurring Transactions) | API pull | MX Platform API — connects to thousands of financial institutions to pull bank transactions and recurring payment patterns. Normalizes bank-sourced transactions into Viacle Purchase Objects with income metadata and recurring series tracking. Supports cross-validation of receipt-derived income streams against bank-reported recurring income. Data types: bank transaction, recurring transaction, recurring income, recurring bill, recurring subscription. | L2 | Registered |
| Akoya Data Access Network | API pull | Akoya — the only 100% API-connected, consumer-permissioned data sharing network. Connects to 4,300+ financial institutions via FDX-aligned APIs. Ingests consumer-permissioned bank transactions (including AI-enriched merchant data, 3-level category hierarchy, and up to 24 months of history) as Viacle Purchase Objects. Supports tax document ingestion (1099s, 1098s) and consent change webhook notifications. Data types: bank transaction, enriched transaction, account, tax document 1099, tax document 1098, consent change. | L2 | Registered |
| Quiltt Open Banking (Plaid · MX · Akoya · Finicity) | API / parse | Quiltt is a unified open banking meta-aggregator that wraps Plaid, MX, Akoya, and Finicity under a single GraphQL + REST interface. One Quiltt connector delivers consumer-permissioned bank transaction data from thousands of financial institutions across all four underlying networks. Ingests posted bank transactions as Viacle Purchase Objects with merchant name, date, amount, and account provenance. Supports both polling sync and webhook-driven ingestion on connection.synced.successful events. Data types: bank transaction, enriched transaction, account, connection sync event. | L2 | Registered |
| Salt Edge Open Banking | API / parse | Salt Edge connects to 5,000+ banks across 50+ countries via PSD2-compliant AIS and PIS APIs. Ingests consumer-permissioned bank transactions from EU, UK, MENA, and global markets as Viacle Purchase Objects. Supports callback-driven ingest when connections are refreshed. Data types: bank transaction, enriched transaction, account, connection callback. | L2 | Registered |
| Taiki Tax Document Retrieval | API / parse | Taiki retrieves tax documents (W-2, 1099-NEC, 1099-MISC, 1099-B, 1099-INT, K-1) directly from financial institutions and payroll providers via user-permissioned authentication. Complements Viacle's TIN-scoped tax aggregation: Taiki brings in verified tax documents, Viacle maps them to purchase-level income records. Tax documents are delivered via webhook after user consent; this connector processes those document payloads. Data types: tax document w2, tax document 1099 nec, tax document 1099 misc, tax document 1099 b, tax document 1099 int, tax document k1. | L2 | Registered |
| Argyle Employment & Income | API / parse | Argyle connects to 500+ payroll providers and gig economy platforms (ADP, Gusto, Paychex, Uber, DoorDash, Lyft) to deliver employer-verified income and employment records. Ingests employment and income data as Viacle income stream Purchase Objects, enriching entity profiles with source-verified employer name, salary, pay frequency, and tenure — the payroll-side complement to Viacle's receipt-derived income inference. Data types: employment, income, paystub, gig activity. | L1 | Registered |
| Truv Income & Employment Verification | API / parse | Truv connects to payroll providers and financial institutions to deliver source-verified income, employment, and asset records. Certified by GSE (Fannie Mae / Freddie Mac) for mortgage income verification. Ingests verified employment and income data as Viacle income stream Purchase Objects, providing employer-confirmed salary, pay history, and tenure as structured records. Data types: employment verification, income verification, income report, paycheck. | L1 | Registered |
| Pentadata (Multi-Aggregator Meta-Layer) | API / parse | Pentadata is a financial data orchestration layer that dynamically routes across Plaid, Finicity, MX, and other aggregators through a single API. Delivers consumer-permissioned bank and card transactions with ML-enriched merchant signals, income verification, Wallet Share (competitive spend intelligence), identity, and full credit file data. FDX-native. 6,500+ institutions. Ingests posted transactions as Viacle Purchase Objects with enriched merchant name, category, and amount. Data types: bank transaction, card transaction, enriched transaction, wallet share, income signal, account. | L2 | Registered |
| Yodlee (Envestnet) Bank Aggregation | API / parse | Yodlee by Envestnet is one of the largest and most established financial data aggregation platforms, connecting to 16,000+ financial institutions globally. Delivers consumer-permissioned bank accounts, credit cards, investment holdings, and transaction history including enriched merchant data, CONTAINER-level account classification, and 1099-ready income signals. Ingests posted transactions as Viacle Purchase Objects with merchant name, category, and high-fidelity amount data. Data types: bank transaction, card transaction, investment transaction, account, enriched transaction. | L2 | Registered |
| Method Financial (Liability Connectivity) | API / parse | Method Financial provides read/write API access to consumer liability accounts — student loans, credit cards, auto loans, mortgages, personal loans, and HELOCs — across hundreds of servicers via a single permissioned API. Fills the structural gap in Viacle's Purchase Graph: where all other connectors cover the asset/transaction side, Method covers the debt side. Ingests payment events and balance changes as Viacle Purchase Objects with liability context, payoff signals, and servicer metadata. Data types: liability account, payment, balance, debt payoff. | L2 | Registered |
| Flinks (Canadian Open Banking) | API / parse | Flinks is the dominant Canadian open banking API, providing live data-sharing with all major Canadian financial institutions (RBC, TD, BMO, Scotiabank, CIBC, and 270+ more). Combines bank connectivity, transaction intelligence, and payment initiation in one API. Fills the Canadian geography gap — all other Viacle bank-feed connectors are US-centric. Ingests consumer-permissioned Canadian bank transactions as Viacle Purchase Objects with enriched merchant name, CAD/USD currency, and account provenance. Data types: bank transaction, account, income signal, cash flow. | L2 | Registered |
| Inverite (Canadian Bank Verification & Cash-Flow Intelligence) | API / parse | Inverite is a Canadian risk infrastructure platform delivering real-time bank verification, income and affordability analytics, and AI-driven cash-flow intelligence. Connects to Canadian financial institutions to verify bank ownership, assess income stability, and generate lending decisioning signals. Complements Flinks (connectivity) with intelligence signals — recurring income detection, NSF risk, affordability scoring. Ingests verified bank transactions as Viacle Purchase Objects with Canadian jurisdiction and income signal metadata. Data types: bank transaction, income signal, cash flow, risk signal, affordability. | L2 | Registered |
| Koxa (Corporate Treasury Open Banking) | API / parse | Koxa connects corporate accounting and ERP systems — NetSuite, Workday, Sage Intacct, Microsoft Dynamics GP, and vertical-specific platforms — directly to corporate bank accounts via open banking APIs. Fills the B2B treasury gap: where all other financial system connectors cover consumer bank feeds, Koxa delivers corporate account transaction data, cash position, and AP/AR payment flows. Ingests corporate bank transactions as Viacle Purchase Objects with organization, GL code, and counterparty metadata. Data types: corporate bank transaction, cash position, ap payment, ar receipt. | L2 | Registered |
| Knot | API / parse | Knot TransactionLink — SKU-level transaction data from linked merchant accounts (Walmart, Amazon, DoorDash, Uber, and more). Financial institutions embed Knot's SDK so end users authenticate their merchant accounts; Knot then fires NEW_TRANSACTIONS_AVAILABLE webhooks and Viacle pulls the full product-level order data including GTIN, unit price, quantity, FSA/HSA eligibility, loyalty tier, tax adjustments, and multi-tender split. Trusted by Amex, Mastercard, Visa, Plaid, PayPal, Klarna, Venmo, and Unit. Data types: line items, gtin, product descriptions, fsa hsa eligibility, loyalty membership, tax adjustments, discounts, multi tender, shipping address, order status. | L3 | Registered |
AP Automation & Expense
Accounts-payable, expense, supplier, and GL-coded data for finance workflows and reconciliation.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| BILL (Bill.com) | API pull | BILL AP automation platform. Ingests paid bills and sent payments as Viacle purchase objects. Auth: session-based (developer key + org ID + username + password). Supports push (webhook: BILL_PAID, PAYMENT_SENT) and pull (List/Bill.json, paymentStatus=paid). Set BILL_WEBHOOK_SECRET to enable HMAC-SHA256 signature verification (X-BILL-Signature). Developer portal: developer.bill.com — self-serve sandbox, no partnership required. Data types: ap invoice, bill paid, payment sent, vendor payment, gl coded invoice. | L2 | Registered |
| Coupa | API pull | Coupa spend management and AP automation platform. Ingests paid invoices as Viacle purchase objects with GL account codes, commodity codes, supplier TIN, and purchase order references. Auth: OAuth 2.0 client_credentials per customer instance (yourcompany.coupahost.com). Supports push (webhook: invoice status=paid/payment_issued) and pull (GET /api/invoices). Set COUPA_WEBHOOK_SECRET to enable HMAC-SHA256 signature verification (X-Coupa-Signature). API documentation: open.coupa.com — customer-credentialed, no platform partnership required. Data types: ap invoice, invoice paid, gl coded invoice, supplier payment, purchase order, commodity code. | L3 | Registered |
| SAP Ariba | API pull | SAP Ariba procurement and AP automation platform. Ingests approved and paid invoices from the Ariba Network as Viacle purchase objects with commodity codes, GL account codes, supplier TIN, and PO references. Auth: OAuth 2.0 client_credentials + API key header + Ariba Network realm ID. Supports push (webhook: invoiceApproved, paid) and pull (Procurement Buying API, OData). Developer portal: developer.ariba.com — self-serve sandbox registration, no partnership required. Data types: ap invoice, invoice approved, invoice paid, gl coded invoice, commodity code, purchase order, supplier payment. | L3 | Registered |
| Tipalti | API pull | Tipalti global payables automation. Ingests completed payments and approved invoices as Viacle purchase objects. Strong in multi-entity, multi-currency global payments (ACH, wire, eCheck, PayPal, prepaid). Auth: API key (Bearer token). Sandbox: api.sandbox.tipalti.com. Supports push (webhook: payment.completed, invoice.paid) and pull (GET /payments?status=paid). Set TIPALTI_WEBHOOK_SECRET to enable HMAC-SHA256 signature verification (X-Tipalti-Signature). Customer-credentialed — no platform partnership required. Data types: ap payment, payment completed, global payables, ap invoice, multi currency payment. | L2 | Registered |
| Stampli | API pull | Stampli AI-driven AP automation platform. Ingests approved and paid invoices as Viacle purchase objects with GL coding, department, project code, and full approver audit trail. Stampli's collaboration model (invoice-level commenting) makes the coding and approval history uniquely rich for expense policy and audit use cases. Auth: API key (Bearer token) + company_id. Supports push (webhook: invoice.paid, payment.sent) and pull (GET /invoices?status=paid). Set STAMPLI_WEBHOOK_SECRET to enable HMAC-SHA256 signature verification (X-Stampli-Signature). Customer-credentialed — no platform partnership required. Data types: ap invoice, invoice approved, invoice paid, gl coded invoice, approval audit trail, department coding. | L2 | Registered |
| Payhawk | API / parse | Payhawk spend management platform (corporate cards, AP automation, expenses). Ingests expenses (card, bank, cash, reimbursable, mileage, per diem) as Viacle purchase objects with supplier tax ID, GL account code, and line-item categorization. Auth: API key (X-Payhawk-ApiKey header), self-serve from Settings → Integrations in the Payhawk Web Portal. Supports push (webhook: expense.created, expense.approved, payment.settled — payload carries only the expense ID, so ingestion fetches the full expense via GET before normalizing) and pull (GET /accounts/{accountId}/expenses). Set PAYHAWK_VERIFY_WEBHOOK_SIGNATURE=true to enable RSA-SHA256 signature verification (X-Payhawk-Signature, public key fetched from Payhawk). Developer portal: developers.payhawk.com — self-serve, no partnership required. Data types: expense, card transaction, bank expense, reimbursable expense, mileage, per diem, gl coded expense, supplier tax id. | L2 | Registered |
Accounting Platforms
Accounting and bookkeeping records, including bills, invoices, journal entries, and account classifications.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| QuickBooks Online | API pull | QuickBooks Online accounting integration. Pushes Viacle purchase objects to QBO as Bills (vendor expenses) with line-item detail. Supports sandbox and production environments. Requires a QBO app with Accounting scope. Data types: bill, purchase. | L2 | Registered |
| Unified.to Accounting | API pull | Stage-1 accounting sync through an authorized Unified.to connection. Data types: accounts, bills, expenses, invoices. | L2 | Registered |
| Xero | API pull | Xero accounting integration. Pushes Viacle purchase objects to Xero as Bills (accounts payable) with line-item detail and merchant contact matching. Supports multi-organisation tenants. Requires a Xero app with Accounting scope. Data types: invoice, bank transaction. | L2 | Registered |
| Omie | API pull | Brazilian cloud ERP/accounting platform for SMBs. Pulls Contas a Pagar (accounts payable) as purchase records, resolving supplier identity (razão social, CNPJ) via the Clientes API. Data types: accounts payable, suppliers. | L2 | Registered |
| Campfire | API pull | Outbound connector for Campfire AI accounting platform. Pushes Viacle purchase objects to Campfire as Bills (accounts payable) with line-item detail, enabling automated journal entry creation and vendor expense tracking. Data types: bill, vendor, journal entry. | L2 | Registered |
| Codat Accounting Aggregator | API pull | Codat unified API for accounting platforms — QuickBooks Online, Xero, NetSuite, Sage, FreshBooks, Wave, and others. Ingests AP bills (BillCreated, BillUpdated) and customer invoices (InvoiceCreated) as structured purchase objects with GL codes from accountRef line items. Data types: BillCreated, BillUpdated, InvoiceCreated. | L2 | Registered |
Billing & Subscriptions
Recurring billing, subscription, invoice, usage, and renewal events.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| Maxio Advanced Billing | API pull | Subscription billing and revenue management for B2B SaaS. Ingests paid invoices and payment webhooks (payment_success, renewal_success, signup_success) with line-item detail. Data types: invoice, subscription payment, renewal. | L2 | Registered |
| Orb | API / parse | Usage-based billing and revenue management for modern software companies (Vercel, Pinecone, Replicate, Airbyte, Dune). Ingests paid invoices with full line-item detail (metered usage lines, quantity, unit price, service period). Handled webhook events: invoice.payment_succeeded, invoice.paid, invoice.manual_payment_recorded. Webhook signature: HMAC-SHA256 over raw body via X-Orb-Signature header. Set ORB_WEBHOOK_SECRET to enable verification. Pull sync: GET /v1/invoices?status=paid (cursor paginated). Auth: Bearer api_key (orb_live_... / orb_test_...). Self-serve sandbox — no partnership required. Data types: invoice, usage line item, subscription invoice. | L3 | Registered |
| Chargebee | API / parse | Subscription billing and revenue management (Freshworks, Okta, Calendly, Envoy). Ingests paid invoices with full line-item detail (plan name, quantity, unit price, service period). Ingestible events: payment_succeeded, invoice_generated, subscription_renewed, subscription_reactivated, subscription_started. Webhook signature: HMAC-SHA256 of raw body via X-Chargebee-Webhook-Signature-V2 header. Set webhook_secret to enable verification. Pull sync: GET /api/v2/invoices?status[is]=paid (cursor paginated). Auth: HTTP Basic — API key as username, empty password. Self-serve sandbox — no partnership required. Data types: subscription invoice, line item, payment, renewal. | L3 | Registered |
| Recurly | API / parse | Subscription management and recurring billing (Sling TV, CBS Interactive, Twitch, BarkBox, Bazaarvoice). Ingests paid invoices with full line-item detail (plan name, accounting code, quantity, unit price). Ingestible events: paid_invoice, successful_payment, subscription_renewed, subscription_reactivated, new_subscription. Webhook signature: HMAC-SHA256 via X-Recurly-Hmac-Sha256 header. Set webhook_secret to enable verification. Pull sync: GET /invoices?state=collected (cursor paginated, API version 2021-02-25). Auth: HTTP Basic — API key as username, empty password. Self-serve sandbox — no partnership required. Data types: subscription invoice, line item, payment, renewal. | L3 | Registered |
| Paddle | API / parse | Merchant-of-record subscription billing and payments (Framer, Canny, Typeform). Paddle acts as seller of record handling VAT/sales tax and payment compliance globally. Supports both Paddle Billing (current, 2023+ API) and Paddle Classic (legacy). Ingestible events: transaction.completed, transaction.paid, subscription.activated, subscription.renewed. Webhook signature: Paddle-Signature header — HMAC-SHA256 of ts:body using webhook_secret. Pull sync: GET /transactions?status=completed (cursor paginated). Auth: Bearer api_key. Self-serve sandbox — no partnership required. Data types: transaction, subscription invoice, line item, renewal. | L3 | Registered |
Commerce, POS & ERP
Commerce, point-of-sale, and ERP systems that provide orders, products, invoices, payments, and supplier records.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| Odoo | API pull | Full-suite ERP with POS, invoicing, accounting, and inventory. Syncs POS orders, purchase invoices, and sales data with complete line-item detail. Data types: pos orders, purchase invoices, sales orders, products, partners. | L3 | Registered |
| ERPNext | API pull | Full-featured ERP by Frappe with accounting, inventory, and POS. Syncs purchase invoices, POS transactions, and supplier data with item-level detail. Data types: purchase invoices, pos invoices, suppliers, items, payment entries. | L3 | Registered |
| FloreantPOS | API pull | Open-source restaurant and retail POS system. Connects to the FloreantPOS database to sync completed tickets with item-level detail and payment methods. Data types: pos tickets, ticket items, payment records, menu items. | L3 | Registered |
| uniCenta | API pull | Multi-language open-source POS for retail and hospitality. Connects to the uniCenta database to sync completed sales tickets with line items and payment data. Data types: sales tickets, ticket lines, payments, products, categories. | L3 | Registered |
| WallacePOS | API pull | Web-based POS system built on PHP and MySQL. Connects via REST API to sync sales transactions, items, and payment data from retail and hospitality environments. Data types: sales transactions, sale items, payment records, product catalog. | L3 | Registered |
| Chromis POS | API pull | Java-based open-source POS system for retail and hospitality. Connects to the Chromis database to extract completed sales tickets, line items, and payment records. Data types: sales tickets, ticket lines, payment records, product catalog. | L3 | Registered |
| Open Source POS | API pull | PHP-based point of sale system for retail operations. Connects via REST API to sync completed sales, item details, payment methods, and customer data. Data types: sales transactions, sale items, payment records, customer data. | L3 | Registered |
| WooCommerce | API pull | Open-source e-commerce platform built on WordPress. Connects via REST API to sync completed orders, line items, shipping, tax, and payment method data from any WooCommerce store. Data types: orders, line items, shipping records, refunds. | L3 | Registered |
| PrestaShop | API pull | Open-source e-commerce platform powering 300,000+ stores worldwide. Connects via Webservice API to sync orders, order details, product data, and payment information. Data types: orders, order details, product catalog, payment records. | L3 | Registered |
| Smartstore | API pull | Open-source ASP.NET e-commerce platform with a modular architecture. Connects via Web API to sync orders, order items, payment data, and product catalog from Smartstore installations. Data types: orders, order items, payment records, product catalog. | L3 | Registered |
| Apache OFBiz | API pull | Enterprise-grade open-source ERP and e-commerce framework by the Apache Foundation. Connects via REST API to sync purchase orders, invoices, payments, and product catalog data. Data types: purchase orders, invoices, payments, product catalog. | L3 | Registered |
| Sylius | API pull | Symfony-based open-source e-commerce platform designed for customization. Connects via Admin API to sync orders, order items, payments, and customer data. Data types: orders, order items, payments, customer data. | L3 | Registered |
| Saleor | API pull | GraphQL-first open-source e-commerce platform. Connects via GraphQL API to sync orders, order lines, payment data, and fulfillment records from Saleor storefronts. Data types: orders, order lines, payments, fulfillments. | L3 | Registered |
| Medusa | API pull | Open-source composable commerce engine built with Node.js (v2). Connects via Admin REST API to sync orders, line items, payments, and fulfillment data. Data types: orders, line items, payments, fulfillments. | L3 | Registered |
| LiteERP | API pull | Lightweight open-source ERP system for small and medium businesses. Connects via REST API to sync purchase orders, invoices, inventory movements, and vendor records. Data types: purchase orders, invoices, inventory movements, vendor records. | L3 | Registered |
| pretix | API pull | Open-source event ticketing platform. Connects via REST API to sync ticket orders, line items, and payment data across organizers and events. Data types: orders, ticket positions, payments. | L3 | Registered |
| Open Food Network | API pull | Open-source food marketplace and distribution platform. Connects via Spree-based REST API to sync orders, line items, and producer payments from local food hubs. Data types: orders, line items, payments, products. | L3 | Registered |
| Commerce Layer | API pull | Headless commerce API platform. Authenticates via OAuth 2.0 client credentials and syncs placed orders, line items, and payment data using the JSON:API-formatted REST API. Data types: orders, line items, payments. | L3 | Registered |
| Openbravo | API pull | Open-source ERP and POS platform. Uses the Openbravo REST Web Services DAL interface to pull sales orders and order lines with full item-level detail. Data types: sales orders, order lines, products, business partners. | L3 | Registered |
| iDempiere | API pull | OSGi-based ERP/CRM/SCM platform. Connects via the iDempiere REST API to pull sales orders (C_Order) and order lines with full product and tax detail. Data types: sales orders, order lines, invoices, products, business partners. | L3 | Registered |
| metasfresh | API pull | Open-source ERP with strong invoicing, procurement, and sales order management. Connects via the metasfresh REST API to pull sales orders and invoice line items. Data types: sales orders, order lines, invoices, invoice lines, products. | L3 | Registered |
| Tryton | API pull | Modular open-source ERP platform. Connects via Tryton's JSON-RPC protocol to pull confirmed sales orders and line items from the sale.sale model. Data types: sales orders, sale lines, invoices, parties, products. | L3 | Registered |
| Square | API pull | Square POS connector. Ingests completed orders from Square as purchase objects with full line-item detail. Supports retail, restaurant, and services merchants. Pulls via Square Orders API v2 using your access token. Data types: orders/completed. | L3 | Registered |
| Clover | API pull | Clover POS connector. Ingests paid orders from Clover as purchase objects with full line-item detail. Supports retail, restaurant, and service merchants. Syncs via Clover REST API v3 using your merchant ID and API token. Data types: orders/paid. | L3 | Registered |
| Shopify | API pull | Shopify e-commerce connector. Ingests paid orders as purchase objects with full line-item detail (title, SKU, quantity, price). Supports webhook-based real-time ingest (orders/paid, orders/fulfilled) and scheduled pull sync via the Shopify Admin REST API. Data types: orders/create, orders/paid, orders/fulfilled. | L3 | Registered |
| Toast POS | API pull | Toast POS connector for restaurants. Ingests paid orders as purchase objects with full guest check, selection, and tender detail. Authenticates via OAuth2 client credentials and pulls from the Toast Orders API. Data types: orders/paid. | L3 | Registered |
| BigCommerce | API pull | BigCommerce e-commerce connector. Ingests completed orders as purchase objects with full line-item, tax, and payment detail. Pulls via the BigCommerce v2 Orders API using a store API token. Supports pagination and incremental sync. Data types: orders/completed, orders/shipped. | L3 | Registered |
| Etsy | API pull | Etsy seller connector. Ingests paid receipts (orders) as purchase objects with full line-item detail, shipping, and tax breakdown. Pulls via the Etsy Open API v3 using a personal OAuth2 access token and your shop ID. Data types: receipts/paid, receipts/shipped. | L2 | Registered |
| STAR Standard Automotive Deal API | API / parse | STAR (Standards for Technology in Automotive Retail) is the automotive industry data standard for dealer management system interoperability. The Deal API provides structured vehicle purchase transaction records — VIN, sale price, financing, trade-in, F&I products, dealer TIN, and buyer information — from participating DMS platforms. Ingests completed vehicle deals as high-value Viacle Purchase Objects, including new/used vehicle sales, lease closings, and fleet transactions. Data types: vehicle sale, vehicle lease, fleet transaction, fi product, sales lead. | L3 | Registered |
| FISPAN (ERP Embedded Banking) | API / parse | FISPAN embeds banking and treasury services directly into ERP and accounting systems (SAP, Oracle, Microsoft Dynamics, NetSuite) under the bank's brand. Banks deploy FISPAN to give business clients payment initiation, account balances, and transaction history inside their ERP — without leaving the workflow. Ingests ERP-embedded payment transactions and AP/AR flows as Viacle Purchase Objects with ERP reference IDs, GL codes, cost centers, and counterparty metadata. Data types: ap payment, ar receipt, bank transaction, erp payment, account balance. | L2 | Registered |
| Rutter (E-Commerce Aggregator) | API pull | Rutter aggregates Shopify, WooCommerce, Amazon, eBay, BigCommerce, Squarespace Commerce, and 10+ other platforms into a single normalised webhook. One Rutter connector replaces individual per-platform connectors. Ingests ORDER_CREATED and ORDER_UPDATED events with full line-item detail. Data types: ORDER CREATED, ORDER UPDATED. | L3 | Registered |
Rental Management
Equipment and asset rental records connected to the underlying transaction and vendor context.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| EZRentOut | API pull | EZRentOut equipment rental management connector. Ingests order lifecycle webhooks — order.checked_out, order.returned, order.invoiced, order.created. Turns each rental order into a Viacle purchase object with full rental_metadata: equipment serial numbers, meter readings, return status, damage waiver, job site, billing cycle, and per-item rate breakdown. Supports construction, healthcare, and general equipment rental businesses. Data types: order.checked out, order.returned, order.invoiced, order.created. | L3 | Registered |
| Point of Rental | API pull | Point of Rental enterprise rental management connector. Supports 70,000+ rental professionals across General Tool, Heavy Equipment, Event & Tent, Aerial & Access, Trench & Shoring, Recreational, Portable Sanitation, and Specialty verticals. Ingests contract lifecycle webhooks (Open, Returned, Off Rent, Closed). Turns each ContractResponse into a Viacle purchase object with full rental_metadata: serial numbers, meter readings (typed: Hours, Fuel, etc.), return status, damage waiver, job site, depot, and per-line rate breakdown. Data types: Reservation, Open, Returned, Off Rent, Closed. | L1 | Registered |
| Record360 | API pull | Record360 equipment inspection connector. Captures inspection.created, inspection.updated, and inspection.completed webhook events from Record360 — the leading mobile inspection platform used by rental yards to document equipment condition at checkout and return. Maps each inspection into a Viacle purchase record with rental_metadata: unit reference number (serial/asset tag), inspection type (open=checkout, close=return, maintenance), damage findings (damage_present), photo/video evidence counts, and location. Enables damage tracking, return condition audit trails, and warranty/liability documentation across your rental fleet. Data types: inspection.created, inspection.updated, inspection.completed. | L1 | Registered |
Identity & KYB
Business identity and registered-entity data used to resolve vendors and establish trusted counterparty context.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| Enigma KYB | API pull | Enigma business identity graph. Enriches merchant records with registered legal name, entity type, registration status, and formation date sourced from Secretary of State filings across all 50 US states. Run sync to bulk-enrich all merchants not yet processed. Data types: business identity, registered entity. | L1 | Registered |
Loyalty & Rewards
Loyalty and rewards data connected to the purchase record for membership, benefit, and post-purchase workflows.
| Connector | Method | Data Output | Level | Status |
|---|---|---|---|---|
| Trifft Loyalty | API pull | Outbound connector for Trifft emotional loyalty platform. Pushes Viacle purchase objects to Trifft as transactions, enabling item-level loyalty points, personalisation, and emotional scoring for your members. Data types: transaction.created, transaction.refunded, member.created, member.fetched. | L2 | Registered |
Don’t see your carrier or platform?
Standard EDI 210 and EDI 214 support may be available where the carrier feed and mapping are configured. For proprietary TMS formats and new connector requests, contact the freight infrastructure team.
This is the static connector catalog — visible without JavaScript.
The interactive version with animations and filter is at viacle.io/integrations.
Source of truth: server/connectors/registry.ts.
Last updated: 2026-08-15.