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
- 01ca45bb914cbd624cf71e18a1ec725a2fc91b2b408f28170ed61effa5659032
- request
- bbf2897a7a008f9c1da734373b645b1b6235d1ee58d374fb914f20b721623478
- transaction
- 9a68da713c6f772c287c5fed4fa262ef346bbe4d42196c15cd768a98a2fa72aecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47013
the chainentry 47013
- sealed to the entry before
- 870be1c340574bf1c445cbe87b1a0db61f7089c67aa171b940abca4f3e7ec262
- this leaf
- 7ef69d961bf30ea360b98aee5e7a9366438468e2ba5eaac3513dd7cf2ed607e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +gz93OZsQ9Z/k4icPFdd4JB9wioXCjB74q+jHzTeOudrhmf5GP3JJBMBkK5jeDzj5p8bVEGC5Xqu5RiG3tMbCA==