Digital Wallet Activity Sequences
This dataset provides detailed, event-level records of digital wallet user activities, including monetary transactions and non-monetary actions, with rich contextual information such as device, location, channel, and session sequence. It enables comprehensive analysis of user behavioral patterns, session flows, and transaction outcomes for engagement optimization and fraud detection. The dataset is ideal for building predictive models, anomaly detection systems, and user segmentation strategies in digital finance.
Sample rows
preview · 8 of 200 rows · all 18 columns| user_idstring | device_typestring | amountfloat | is_successfulboolean | currencystring | activity_sequence_idstring | transaction_idstring | activity_typestring | activity_timestampdatetime | merchant_idstring | location_citystring | location_statestring | location_countrystring | ip_addressstring | failure_reasonstring | user_balance_afterfloat | channelstring | sequence_orderinteger |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| u101 | mobile | blank | true | blank | seq101 | tx10001 | login | 2024-03-12T08:12:17Z | blank | San Francisco | CA | US | 172.24.10.55 | blank | blank | app | 1 |
| u101 | mobile | blank | true | blank | seq101 | tx10002 | balance_check | 2024-03-12T08:12:29Z | blank | San Francisco | CA | US | 172.24.10.55 | blank | 2380.12 | app | 2 |
| u101 | mobile | 122.55 | true | USD | seq101 | tx10003 | payment | 2024-03-12T08:13:05Z | m2211 | San Francisco | CA | US | 172.24.10.55 | blank | 2257.57 | app | 3 |
| u101 | mobile | blank | true | blank | seq101 | tx10004 | logout | 2024-03-12T08:13:16Z | blank | San Francisco | CA | US | 172.24.10.55 | blank | blank | app | 4 |
| u202 | desktop | blank | true | blank | seq102 | tx10005 | login | 2024-03-13T17:19:51Z | blank | Chicago | IL | US | 192.168.4.78 | blank | blank | web | 1 |
| u202 | desktop | 400 | true | USD | seq102 | tx10006 | top-up | 2024-03-13T17:20:15Z | atm301 | Chicago | IL | US | 192.168.4.78 | blank | 800 | web | 2 |
| u202 | desktop | 50 | false | USD | seq102 | tx10007 | transfer | 2024-03-13T17:21:08Z | u303 | Chicago | IL | US | 192.168.4.78 | Recipient account restricted | 800 | web | 3 |
| u202 | desktop | blank | true | blank | seq102 | tx10008 | logout | 2024-03-13T17:21:23Z | blank | Chicago | IL | US | 192.168.4.78 | blank | blank | web | 4 |
| uk99 | mobile | blank | true | blank | seq103 | tx10009 | login | 2024-03-14T06:45:09Z | blank | London | ENG | GB | 81.105.32.44 | blank | blank | app | 1 |
| uk99 | mobile | blank | true | blank | seq103 | tx10010 | balance_check | 2024-03-14T06:45:27Z | blank | London | ENG | GB | 81.105.32.44 | blank | 120.5 | app | 2 |
| uk99 | mobile | 12 | true | GBP | seq103 | tx10011 | payment | 2024-03-14T06:46:08Z | m8819 | London | ENG | GB | 81.105.32.44 | blank | 108.5 | app | 3 |
| uk99 | mobile | blank | true | blank | seq103 | tx10012 | logout | 2024-03-14T06:46:18Z | blank | London | ENG | GB | 81.105.32.44 | blank | blank | app | 4 |
| u303 | pos_terminal | 1000 | true | USD | seq104 | tx10013 | withdrawal | 2024-03-15T10:11:03Z | atm101 | Miami | FL | US | 10.12.11.99 | blank | 2500 | pos | 1 |
| u303 | pos_terminal | 2000 | false | USD | seq104 | tx10014 | withdrawal | 2024-03-15T10:13:12Z | atm101 | Miami | FL | US | 10.12.11.99 | Insufficient funds | 2500 | pos | 2 |
| fr55 | desktop | blank | false | blank | seq105 | tx10015 | login | 2024-03-16T20:09:17Z | blank | Paris | IDF | FR | 2a01:cb00:1234:56::1 | Incorrect password | blank | web | 1 |
| de88 | desktop | blank | true | blank | seq106 | tx10016 | login | 2024-03-17T02:13:44Z | blank | Berlin | BE | DE | 185.36.89.21 | blank | blank | web | 1 |
| de88 | desktop | blank | true | blank | seq106 | tx10017 | balance_check | 2024-03-17T02:14:02Z | blank | Berlin | BE | DE | 185.36.89.21 | blank | 982.12 | web | 2 |
| de88 | desktop | 100 | true | EUR | seq106 | tx10018 | transfer | 2024-03-17T02:15:09Z | fr55 | Berlin | BE | DE | 185.36.89.21 | blank | 882.12 | web | 3 |
| de88 | desktop | blank | true | blank | seq106 | tx10019 | logout | 2024-03-17T02:15:22Z | blank | Berlin | BE | DE | 185.36.89.21 | blank | blank | web | 4 |
| ind1 | mobile | 6000 | true | INR | seq107 | tx10020 | top-up | 2024-03-18T12:00:01Z | atm175 | Mumbai | MH | IN | 112.133.194.251 | blank | 12000 | app | 1 |
What the 200 rows show
from the 200-row sample- 77%is_
successful = true - 190.3median amount
- 6channels
- 10activity types
- 21location countries
- 29location cities
Median 190.3, from 0.0 to 100,000,000.
- string 13
- integer 1
- float 2
- datetime 1
- boolean 1
Columns
18 columns in four groups| column | type | description | example |
|---|---|---|---|
| Text 13 columns | |||
user_id | string | Unique identifier for the digital wallet user | u101 |
activity_sequence_id | string | Unique identifier for a specific activity sequence or sessionunique | seq101 |
transaction_id | string | Unique identifier for each transaction within the activity sequenceunique | tx10001 |
activity_type | string | Type of activity or transaction (e.g., payment, transfer, top-up, withdrawal, login, logout, failed_attempt)10 values | login |
currency | string | Currency code (ISO 4217) for the transaction, e.g., USD, EUR; null for non-monetary activitiesoptional | USD |
merchant_id | string | Identifier for the merchant or recipient involved in the transaction, if applicableoptional | m2211 |
device_type | string | Type of device used for the activity (e.g., mobile, desktop, tablet, POS terminal)mobile · desktop · tablet · pos_terminal · other · optional | mobile |
location_city | string | City where the activity occurred, if availableoptional | San Francisco |
location_state | string | State or province where the activity occurred, if availableoptional | CA |
location_country | string | Country where the activity occurred (ISO 3166-1 alpha-2 code), if availableoptional | US |
ip_address | string | IP address from which the activity was performed, if availableoptional | 172.24.10.55 |
failure_reason | string | Reason for failure, if the activity was not successful; null if successfuloptional | Insufficient funds |
channel | string | Channel through which the activity was performed (e.g., app, web, USSD, API, POS)6 values · optional | app |
| Numbers 3 columns | |||
amount | float | Transaction amount in the wallet's currency; null for non-monetary activities0 or more · optional | 122.55 |
user_balance_after | float | User's wallet balance immediately after the activity; null for non-monetary activities0 or more · optional | 2380.12 |
sequence_order | integer | Order of the activity within the activity sequence (starting from 1)1 or more | 1 |
| Dates and times 1 column | |||
activity_timestamp | datetime | Date and time when the activity occurred | 2024-03-12T08:12:17Z |
| True or false 1 column | |||
is_successful | boolean | Indicates if the activity or transaction was successful | true |
Use it for
A finance dashboard
The is_
successful rate, amount by device_ type and a breakdown of currency. Excel, Power BI or Tableau. Why do 153 of 200 rows have is_
successful = true? A class exercise
Hand out the rows and one question. Everyone works from the same 200 rows.
- Users200u101mobileu101mobileu20250desktop
A software demo
Believable users with activity_
sequence_ id, transaction_ id and activity_ type to fill a screen in front of a buyer.
blueprint · digital-wallet-activity-sequences
Behind this dataset
Same schema. As many rows as you need.
These 200 rows came out of a blueprint — 18 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.
- Sequential user events per wallet ID.
- Payment, top-up, and transfer activities tagged.
- Device and geolocation metadata attached.
- Fraud risk levels annotated.
1 credit per row. Preview 20 rows free. Buy rows for the full run.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- digital-wallet-activity-sequences