Where Does the Esso Pay App Store Data?
Esso Pay fuel payment keeps cards in private storage on Android and iOS under a firstdata ID. The saved view returns after login.
Last updated
Fuel brand Esso runs its Pay app under a firstdata processor ID on Android with a matching iOS build. Private storage holds login session plus card cache. The processor string belongs to the payment backend, which is why brand searches miss the folder.
Payment cards live server side. Fresh login restores cards after reinstall. Pump unlock codes generate per transaction and never sit in local files. Private storage holds the local copy. Account data survives reinstall. Cached images reload on demand. Local copies clear without account loss. Local state reflects the account.
Where Esso Pay stores this, by platform
/data/data/com.firstdata.esso_germany
Private session and card cache for the verified firstdata package. Cards sync from servers after login.
/var/mobile/Containers/Data/Application/<guid>/Documents
GUID container for Esso Pay (App Store ID 1449167509). Re login restores cards.
Frequently asked questions
Do Esso cards transfer phones?
Log into the same account on the new phone. Cards sync from servers, including loyalty balances. Local data holds session and station cache, so the move needs no file copies.
What is the exact Esso package name?
The verified ID is com.firstdata.esso_germany from the payment processor. Quote the full firstdata string; esso guesses match nothing on device. Login restores the saved view.
Notice an outdated path? Let us know.