Articles on: Integrations & Connections

Setting Up Stripe Identity in Fleetwire

Verify your renters with Stripe Identity


Fleetwire works with Stripe Identity to check that each renter is who they say they are. The renter photographs their driver's license and takes a quick selfie on their phone; Stripe confirms the license is genuine and that the face matches. The result, including date of birth, license number and expiration date, appears on the booking and the customer's profile.


To connect it, you create a restricted API key in Stripe that lets Fleetwire run ID checks and nothing else, lock it to Fleetwire's server address, and paste it into Fleetwire. Setup takes about five minutes.



✅ Before you begin


  • Stripe Identity is enabled on your Stripe account. You should be able to create a verification session by hand in your Stripe Dashboard.
  • You're a company admin in Fleetwire. Only admins can save or change the Stripe Identity key.


Some Identity permissions don't appear in Stripe until Identity is fully enabled on your account, so finish that first.



🔐 Step 1: Create a restricted key in Stripe


  1. Open your Stripe API keys page and click Create restricted key.
  2. Name it something you'll recognize, like Fleetwire ID Key.
  3. Set these permissions. Leave everything else at None.


Section

Permission

Set to

All core resources

Files

Write

Identity

Identity Verification Results

Write

Identity

Recent Detailed Verification Results

Read


  1. Click Create key, then copy the key. It starts with rk_live_.



🔒 Step 2: Allow Fleetwire's IP address


Stripe only lets Fleetwire read ID details older than 48 hours if the key is locked to Fleetwire's server address:


134.199.185.80


Stripe shows one of two screens, depending on your account. On the API keys page, open the ⋯ menu next to your new key:


If you see "Manage IP restrictions":

  1. Choose Manage IP restrictions.
  2. Add 134.199.185.80 (leave the CIDR toggle off) and click Save.


If you see "Manage access policy" instead:

  1. Go to the Access policies tab (next to API keys) and click Create a policy.
  2. Name it Fleetwire. Leave "Default policy for new keys" unticked, or every key you create later would only work from Fleetwire's server. Click Continue.
  3. Choose IP addresses, add 134.199.185.80, and finish creating the policy.
  4. Back on API keys, open ⋯ → Manage access policy on your Fleetwire key, choose the Fleetwire policy, and save.


Set up before October 2026? Your key is probably locked to our old address, 138.68.28.176. Add 134.199.185.80 the same way (to the key's IP restrictions, or to its access policy), then remove the old address. ID checks keep working while you switch.



⚙️ Step 3: Turn on long-term access to ID details


  1. Open the ⋯ menu next to the key again and choose Edit key (older screens say Edit).
  2. In the Identity section, set:
    • All Detailed Verification Results → Read
    • Recent Detailed Verification Results → None
  4. Click Apply changes.


Why? This lets Fleetwire show a renter's date of birth, license number and expiration date on the booking at any time, not just in the first 48 hours, and include the license photos in dispute evidence. Stripe only allows it on keys with an IP restriction, which is why Step 2 comes first.



🔗 Step 4: Add the key to Fleetwire


  1. In Fleetwire, go to Settings → Integrations → Connections: tenant.fleetwire.io/settings/providers#integrations
  2. On the Check ID with Stripe card, paste the key into Stripe RESTRICTED key and click Save.


Fleetwire encrypts the key and never shows it again; you'll only see that a key is set. To replace it later, reset it and paste the new one.



🪪 What your renters see


When you request an ID check, your renter gets a secure Stripe link. They:


  1. Take a live photo of the front and back of their driver's license (uploaded photos aren't accepted).
  2. Take a selfie, which Stripe matches to the license photo.


The outcome — verified, or the reason it failed — shows up on the booking.



🛠️ Troubleshooting


What you see

What to do

"The API key provided does not allow requests from your IP address"

Your key's IP restriction or access policy doesn't include Fleetwire's address. Add 134.199.185.80 (Step 2).

"Expired API key provided"

The key was rolled or expired in Stripe. Create a new restricted key (Steps 1–3) and save it in Fleetwire (Step 4).

A permission error, or the license details are missing on a verified renter

Open the key in Stripe (⋯ → Edit key) and check Steps 1 and 3.

Stripe says "Access to all detailed verification results can only be added to keys that have configured an IP allowlist"

The key has no IP restriction or access policy yet. Do Step 2 first, then Step 3.

Identity permissions aren't listed in Stripe

Stripe Identity isn't fully enabled yet. Create one verification session from your Stripe Dashboard, then try again.


Still stuck? Chat with us and we'll check your setup with you.



🎥 Video walkthrough


The video uses Stripe's older permission names and our old IP address. Use the steps above: the IP to add is 134.199.185.80.


Updated on: 29/10/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!