Coast Fuel Card Integration

• Overview
• Integration Summary and Key Benefits
• Integration Setup Process
• Integration Setup Steps
• Technical Details
• Error Handling and Troubleshooting

Overview 

The Coast–Azuga integration connects Coast’s Visa-powered fuel card platform with Azuga’s telematics system to streamline fleet expense management and enhance fraud prevention. By automatically verifying vehicle location at the time of purchase and collecting odometer readings from Azuga, fleet managers can reduce administrative work, gain better visibility into fuel expenses, and improve fraud detection.

Integration Summary and Key Benefits 

Automatic Transaction Ingestion

• Coast purchases are instantly recorded in the Coast portal.
• When integrated with Azuga, transactions are enriched with telematics data, such as GPS location and odometer readings.

Location-Based Fraud Detection

• Coast automatically verifies the vehicle’s last known GPS location from Azuga.
• If the vehicle is too far from the fueling station, Coast can decline the transaction, preventing fraud and unauthorized purchases.

Odometer Data Collection

• Azuga automatically adds odometer readings to fuel transactions in Coast.
• This enhances fuel efficiency tracking (MPG), maintenance scheduling, and driver performance analysis.

Vehicle Data Synchronization

• Coast regularly imports vehicle details (VIN or license plate) from Azuga.
• This reduces manual data entry and ensures both systems maintain accurate vehicle records.

Expense Consolidation and Policy Controls

• Fleet managers can set spending limits and restrict purchase categories (e.g., fuel only, maintenance, car washes) within Coast.
• Real-time alerts and spend reports provide greater control and visibility into fleet expenses.

Integration Setup Process 

To begin, ensure you have active accounts with both Coast and Azuga. The following sections detail the prerequisites, setup steps, technical considerations, and support expectations.

Prerequisites

✅ Coast Account and Portal Access

• An active Coast account with administrative privileges is required to install and manage integrations.

✅ Azuga Account and Credentials

• A valid Azuga account with the necessary credentials (username and password) is required to authorize Coast to access vehicle data.

✅ Vehicle Identifiers

• Ensure that VIN or license plate details in Azuga match those in Coast for accurate vehicle mapping.

✅ Policy Configuration (Optional)

• If you plan to decline fuel purchases based on GPS location, configure your Coast policy settings accordingly (e.g., set the maximum allowed distance from the station).

Integration Setup Steps 

1. Open the Integrations Page in Coast

• Log into your Coast portal.
• Navigate to the Integrations page and locate the Azuga integration card.

2. Install the Azuga Integration

• Click on the Install button.
• You may be asked to re-enter your Coast administrator credentials for verification.

3. Authorize and Connect to Azuga

• Once the installation is complete, click Manage on the Azuga integration card.
• Select Connect and enter your Azuga credentials.
• Coast will request authorization to access Azuga vehicle data.

4. Vehicle Data Sync

• Upon successful authorization, Coast will import vehicle data from Azuga.
• Any vehicles with matching VIN or license plates will automatically sync and begin receiving telematics data (GPS location, odometer readings).
• If a vehicle in Azuga does not match an existing vehicle in Coast, an error will appear. Update the vehicle’s license plate or VIN in either system to resolve the discrepancy.

5. Manage Vehicles and Auto-Sync

• Click Manage Vehicles to view the status of each vehicle.
• Select Vehicles to Import or enable Auto-Sync for any new vehicles.
• Coast checks for changes three times per day (5 a.m., 11 a.m., and 5 p.m. EST) and imports any new or updated vehicles.

6. Configure Fraud Protection (Optional)

• If you want Coast to decline fuel purchases when the vehicle’s last known GPS location is more than one mile from the station, enable this feature in Policy Settings.
• This ensures that out-of-range purchases are automatically declined.

7. Verify Data Flow

• After setup, test a few transactions to confirm that Coast is receiving vehicle location and odometer data from Azuga.
• In Coast, check the Transactions page to verify that odometer readings and GPS-based approvals/declines are working as expected.

Technical Details 

How Coast Integrates with Azuga

• API Integration: Coast retrieves Azuga telematics data via Azuga’s API once authorized, with no need for manual file handling or SFTP. Data synchronization occurs automatically.
• Vehicle Identification: Coast requires a matching VIN or license plate between Azuga and Coast for accurate vehicle mapping. Missing or incorrect identifiers can result in import errors, which can be resolved by updating records in either system.
• Odometer Data Collection: Each fuel transaction in Coast is automatically tagged with the latest odometer reading from Azuga. If the data is unavailable due to a device issue, Coast prompts drivers to enter the odometer reading manually.

Transaction Monitoring and Fraud Protection

• Location-Based Verification: Coast cross-references the vehicle’s last known GPS location from Azuga with the fueling station’s address.
• Fraud Detection: Transactions occurring beyond a predefined distance (e.g., more than 1 mile from the vehicle’s last known location) can be flagged or automatically declined if this setting is enabled in Coast.

Data Flow and Processing

• Vehicle Data Sync: Coast syncs vehicle data from Azuga multiple times per day (5 a.m., 11 a.m., and 5 p.m. EST).
• Transaction Processing: Transactions appear in Coast as soon as they are posted, with additional telematics data from Azuga being added at the next scheduled sync interval. Real-time data push is not currently supported.

Error Handling and Troubleshooting 

Below are common issues and resolutions. For more detailed assistance, reach out to customercare@azuga.com