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
- 5edf5174788f1365a3500d9170aa6f421cf60e73ae5bf911027584b96a5d894f
- request
- 3d7d4fd11bd8f70aa688edab9b8b17fd830d6b8b19d59889410edaef32073f56
- transaction
- ed08760bfc563888de29e78608cd08851c3278d369509cfd23a3ff4429914958computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26523
the chainentry 26523
- sealed to the entry before
- 300722cf01589dbe0f4422c4a6f25e017495df810ffe6d1479f7955033e3ee7b
- this leaf
- 65400cff0ecb3dad315bd0ac573c328e5c17645f1202ce9e3ef4afa06316ceb4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8dTEvO64En1qXA9re/HSiUGm1UkWRsWFofgdLD1Hv7em9XJwyP6QZj06ESIWVKksQRD44SE837BvP/uY9XbbCA==