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
- d28704f2353b52beffc90ec8b98ba314f9d4ccdec85b745fc8023d1322222a31
- request
- 8f4d78fec78114b8ed6608272122aff169a0ec703ccb60632ef92cf1909202b9
- transaction
- f5ba91d92836e3626cd35fa50743b1a8528bc36e8aaebc48a16f92582816d263computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4381
the chainentry 4381
- sealed to the entry before
- ecd642c70aa472783c46302695ac370a09ac0f66833cd777e337d9876a2028c4
- this leaf
- ac1312c02044b35b6fad96ee1993882b02b194daa451a0b6c255761a613b34e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VdkHzJgxoGFX3mFvvzA3Dv8X1f2EtffU/o7cKkMf6SxmvLDYxjb47oLTMNnAC4R5M0xzBi6KbuFRkSGrgrKXBA==