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
- 0d0277e57b365fbfe53501e5f374a363e25ac84944b5c018908666edad8d547d
- request
- ff528dac03ec4c47825d9893c67455153c24e9c92022239847c82c42c88d1535
- transaction
- 3209309f1e1d34e81e562dcf28c0c227f0c8c33cd87de29a7cfef9d3097fbf97computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71930
the chainentry 71930
- sealed to the entry before
- 39ddcb5b6cf2d2c5e423f11a24ea083a8bd04ee36d4f53c9aecb929214fbf009
- this leaf
- db0e9ef7bd5a0ed9322010169d50ea1d8d71abfad02589b792d909fd6f2a2168
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qytM+w7LvRN3PmPsQHQXYLVhMcowNlg9dZqMJ13MKw5bwc6iF9FsPSM3WuY2JUScHBvKgEwZpAkMyDwRDmXGCw==