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
- 63e0a25624fe35d52de4148aa50758ee4b895ae2a266a31a38ebb7affa0dbe8c
- request
- d612bd212dc9ea88ac30cdfb8351645894887166fa040d46f19f2c67db432604
- transaction
- db43717977af3cbe1470a400730615b99ed1bcc2b9c02ea7c55df325ad893cbfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 261
the chainentry 261
- sealed to the entry before
- e1d250e86acb78a345ddfef24b4f23a6382da3600a52c48c755f37a254932181
- this leaf
- b64a5a3324babbc8f559e49799368d1829935b742335e6625e9756949fd86864
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LMIfHUv0NRFaZKuo0+qgwE6yEdw07tazrlWpgks7teL566+3ta0XLY0cwDEejAZ2KzhrLahCBZVjK7cAS4yBCQ==