Access transaction reports via SFTP

When your organization is connected to Lyft’s SFTP server, you will have access to reports that are automatically generated for your Lyft Business account.

The Reports directory

You can find the automatically generated reports in the reports directory folder, /reports/. These reports are generated by the Lyft system and will be uploaded automatically using the Reports Sync via SFTP.

We highly recommend that you do not upload any additional files to the /reports/ folder. You can think of this folder as read-only and there will not be any cases where you will need to upload additional files.

Report types

Reports Sync will generate transactional reports for three products:

  • Business Profiles rides that were not paid for using Auto Pay
  • Auto Pay rides
  • Lyft Pass

Here is an example of a file name you would see in the /reports/ folder:

transaction_report-{organization_id}-{report_type}-{start date}-{end date}.csv

  • {organization_id} will display your actual organization ID
  • {report_type} can be the following type of reports:
    • AutoPay= direct_billing
    • Business Profiles (non AutoPay)= non-db-bp
    • Transactions that are Credits = Transaction_lfw_credits
  • {start date} and {end-date} are exclusive and are always in the format of YYYY-MM-DD

Reading your transactional-based reports

The daily reports generated by Reports Sync are useful for ride trend and cost analysis. The reports contain rows based on all the transactions from each ride your employees take.

A transaction in a ride is defined by a single, specific financial activity that can occur for a ride — credit card charge, usage of a coupon, refunds, etc. In the daily reports, each row represents a transaction. It’s most common for a single ride to have a single payment transaction and be represented by a single row in the daily report.

It is possible for a single ride to have multiple transactions and be represented by multiple rows in the daily reports. This happens most commonly in 4 cases below:

  • Ride cost is split between multiple passengers, generating individual transactions on credit cards of different passengers
  • Ride cost is partially paid by a coupon, resulting in a lower transactional cost for the ride on the credit card
  • Passenger adds a tip to the ride or is charged with additional fees after the ride completion, resulting in tip/fee amount added to a ride after the actual ride date
  • Passenger took a ride and then requested a refund

When a single ride has multiple transactions and is represented by multiple rows in the daily report, the ride-specific fields remain the same across the rows, while transaction-specific fields have their own values based on the individual transaction.

  • Ride-specific fields include: ride ID, request, pickup/dropoff, ride fare, tip, etc. are ride-specific fields since they are attributes belonging to a single ride
  • Transaction specific fields include: name, email, transaction amount, etc. since they are attributes belonging to a financial transaction
Learn more about the definition of each field and its output format in a report, and see a sample CSV file that would be generated by Reports Sync


Report delivery and access

The transactions of a ride will become available to view on a report 24-48 hours after the ride has been completed, depending on when the payment for the ride was processed.

Reports will be generated in the /reports/ folder based upon the cadence in which your organization chooses — daily, weekly, or monthly.

Reporting updates

Once a report is generated, it cannot be updated or modified automatically by our system. For example, if a user retroactively changes their past ride from a business ride to a personal ride, or vice versa, the past transactional reports will not be updated.

Report Availability

Files will stay in the /reports/ folder indefinitely and will not disappear unless you delete them.

Back to top