AtoB API
AtoB is a fleet payments platform that issues fuel and spend cards, enforces granular controls (fuel-only, MCC/category restrictions, per-transaction and daily limits), prevents fraud using telematics-aware rules, and streamlines driver payouts—all with reporting that helps fleets man
What is AtoB?
AtoB is a cloud fintech platform for transportation and logistics fleets that centralizes payments, fuel spend, and driver financial workflows. Teams use AtoB to issue fuel cards (Visa acceptance), configure card controls and fraud prevention, locate discounted stations, pay drivers, and report on transactions for accounting and compliance.
Core product areas include:
- Fleet Payments & Fuel Cards (acceptance network, discounts, statements)
- Spend Controls (fuel-only, MCC restrictions, per-transaction/daily limits, time windows)
- Fraud Prevention & Telematics (geofenced approvals, odometer capture, location checks)
- Driver App & Payouts (earnings, instant pay, card disbursements)
- Reporting & Compliance (IFTA fuel tax data, merchant/category analytics)
Common data entities:
- Companies, Users, Roles/Permissions
- Drivers and Vehicles (assignments, identifiers)
- Cards (status, controls, PAN tokens, PIN configuration)
- Transactions (authorizations, settlements, gallons, product type, merchant, MCC)
- Merchants/Stations (location, brand, discounts)
- Payouts and Earnings (amounts, methods, status)
- Statements and Reports (periods, totals, jurisdictions)
The AtoB Integration Challenge
Fleets rely on AtoB daily, but turning portal-based workflows into API-driven automation can be tricky:
- Real-time controls: Card control updates and authorization outcomes depend on multiple rules (MCC, time-of-day, geofence, odometer), which must be applied consistently and quickly.
- Enterprise security: Admin access typically uses MFA, and card/account data is sensitive; integrations must avoid handling raw PANs and adhere to PCI-safe patterns.
- Portal-first features: Many capabilities (policy updates, driver assignments, payouts) are optimized for the web app and mobile flows; structured exports can be limited.
- Settlement vs. authorization: Transaction lifecycles include pre-auth, completion, and settlement timing—developers need normalized states to avoid double counting.
- Operational realities: Fleets report pain points like inconsistent merchant naming, delayed statement availability, or card declines due to overly strict controls; integrations should add observability and guardrails.
How Supergood Creates AtoB APIs
Supergood reverse-engineers authenticated browser flows and network interactions to deliver a resilient API endpoint layer for your AtoB tenant.
- Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection
- Normalizes responses (cards, drivers, transactions, payouts) into consistent resource schemas
- Aligns with customer entitlements and role-based permissions to ensure compliant access
- Redacts sensitive payment data and uses tokenized identifiers to remain PCI-safe
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened AtoB adapter tailored to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as AtoB evolves.
API Endpoints
Authentication
/sessionsEstablish a session using credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short-lived auth token maintained by the platform.
Authentication
/sessions/refreshRefresh an existing token to keep sessions uninterrupted.
Cards & Controls
/cards/{cardId}/controlsUpdate card controls and assignments (fuel-only rules, MCC whitelist, spend limits, geofence, odometer requirements).
Transactions
/transactionsList transactions (authorizations and settlements) with rich filters and line details.
Driver Payouts
/drivers/{driverId}/payoutsCreate a payout to a driver (instant or scheduled) with memo and external references.
Use Cases
Card Control Automation
- Enforce fuel-only rules, MCC whitelists, and time windows programmatically - Adjust per-transaction and daily limits by route, job, or driver status - Assign cards to vehicles and drivers with required odometer capture
Transaction Sync & Analytics
- Mirror authorized and settled transactions into your data warehouse - Build dashboards for gallons, product mix (diesel/gas/DEF), price-per-gallon, taxes - Flag anomalies (off-route fueling, excessive unit price) and trigger workflows
Driver Payroll and Disbursements
- Automate instant payouts tied to completed loads or time sheets - Reconcile disbursements against earnings and advances in your TMS/payroll system - Provide payout status updates back to driver and ops portals
Telematics-Aware Fraud Prevention
- Integrate with location data to drive geofenced approvals - Log odometer and GPS at time of fueling for audits and IFTA support - Alert when transactions occur outside approved windows or areas
IFTA & Compliance
- Produce jurisdictional summaries of gallons and spend - Attach route and odometer to transactions for audit completeness - Export statements and reports to accounting/ERP
Technical Specifications
Authentication
Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials
Response format
JSON with consistent resource schemas and pagination across modules
Rate limits
Tuned for enterprise throughput while honoring customer entitlements and usage controls
Session management
Automatic reauth and cookie/session rotation with health checks
Data freshness
Near real-time retrieval of cards, transactions (auth and settlement), and payout statuses
Security
Encrypted transport, scoped tokens, and audit logging; redaction of PANs and tokenized financial identifiers; respects AtoB role-based permissions
Webhooks
Optional asynchronous delivery for transaction settlements, card control changes, and payout lifecycle events
Latency
Sub-second responses for list/detail queries under normal load
Throughput
Designed for high-volume transaction sync and control updates across large fleets
Reliability
Retry logic, backoff, and idempotency keys minimize duplicate actions
Adaptation
Continuous monitoring for UI/API changes with rapid adapter updates
Frequently asked questions
Supergood supports commonly used areas such as Cards & Controls, Transactions (authorizations and settlements), Driver/Vehicle assignments, Payouts/Disbursements, and Reporting/Statements, subject to your licensing and entitlements. We scope coverage during integration assessment.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. Sessions are refreshed automatically with secure challenge handling.
Yes. We normalize transactions and statements to match your ERP or accounting schema (e.g., NetSuite, QuickBooks) and deliver updates via webhooks or polling while complying with rate and permission constraints.
Yes. We can ingest telematics/location signals and attach them to authorizations. Control updates can include geofences and odometer requirements for fraud prevention and IFTA support.
Portal-first workflows, limited public APIs, strict card controls causing unexpected declines, and settlement timing differences are typical pain points. Supergood adds observability (events, status mapping), safe retries, and consistent schemas to reduce operational friction.