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
- 8c3da4bc1a0533ee37373a16ad488f1e62da9c85374241bb9c0696d811957d9e
- request
- 6b9c0d7cefd0ccd1c4f822458220da93541110d1012954f8df871301170f60b4
- transaction
- 5c0b116907fa1a73120dbc49054373e33a71fec2cdb70aa5500ed60fa702cd7bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31807
the chainentry 31807
- sealed to the entry before
- c4e19a474bc0d50a603f7c9c1d5e77a7463c6e9309c2ce027e111f1c52335d1c
- this leaf
- bb651b7c7c124ac679046377d9d4a3d0a0ac44a3c75e1bf735e1fd5d4d37824d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eB/tYT6QipGKs2eAvNKdbN3gqCfheDh4z3aqxLlA0DJF5CMv+55s7PayRqDbTS2B9QCTTWuuATLXYmmyIPcXCQ==