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
- 0fe38dc111eacea08e4a20fae0bd34520240d497bc190274bd1c6767a0025011
- request
- 9e71f60882db138a3734d521220ad48dd54c9d5e94c79a25e1fb6ae8fad09b79
- transaction
- 15e1cdccf76508d5f22c2290c86a53d64aa28e33e59be1751c5c8e437c8cdb29computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67716
the chainentry 67716
- sealed to the entry before
- e239b71fc9d38ca8a7a48f49df1e9d33be83b6a171733dd3854dbf0c475371f9
- this leaf
- 6538644dcecbe9c9d66d0613e507c228f4989d4f34e0298d0617d8b1ce3b6aec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a9inUxv5zWCA2911iqKeJugiuUgoFaLif4C8fIlgkT6HQIhjTsfJR9OzFJRCapZMIkylm3P+gy4IRPcYyhDtAg==