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
- 0b1c09f549a83be29d4d34c1c9d512d1436b2588067e9bd6280a15b8593b5e97
- request
- 890d2fddbaf9ecd33d0cd84c2ef2e50e3c71e22cbf01637ed451fa2a1a296757
- transaction
- afcde8be4287ee4282bc9e0149efbe5a7900404886b950ca060019078e930805computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74463
the chainentry 74463
- sealed to the entry before
- 32059e17853137bae3bf4e785580ecccee5e6605e68a4fb068fc4f4e6973b14f
- this leaf
- fcfc235544ee948080beab1f177b4c1c0771016bd25ced3cbe64979932c33bff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0iGMvpQvt9IuB6NteRsk3LcySFpDIbWHuq1RWVr3bQaxpfkAg8SS+NyjRJ7xqR+B9k8sVTBw8ij7+XrJfLe/Cg==