why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 67932566dc63dbf6ed654ca761e84be38072a083b205484ed3d7ad69ce790473
- request
- de5d34b9a75b1825dbb6d0360b6a275ec6153b8ec6f7a5490db4d48a6ad8d47c
- transaction
- 80dcc46bf97a5282dcec346e154a026d648d86ab08c29895743b6f84daf0949ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25620
the chainentry 25620
- sealed to the entry before
- 25875ecd869a76d8631b1aefb19dd0972dabf6ea2e83a11ae0e9a1154623a7a2
- this leaf
- 285dd5c7bcdcc4ee34e5488f0c9737ce8e5d39c3e9b9b31bbade24840fa60494
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ItKn76pFl+f1mD33zsUloCANRSo/BNSFT/hmjOo6ijVZc3y86jg9V88p8kSdtZlEY6/wSMiFj3pIDqY9DZqSCw==