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
- dcbdf35a194beb059c486f2afec91c0b532e4ca829ec2fb3da49ac93c11303d5
- request
- a1dea0dbd8cba86345cb2790123ff09717ebfa28d2dd9ca1df97d6f006611eca
- transaction
- 763f63c0491b0be8336f98befac03d635cc39f290d266ae6b0886ac2243b4feecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48415
the chainentry 48415
- sealed to the entry before
- 864720701b846fbda001c3556184946f1fbf0ce35659484e4f1c3be8564edbc4
- this leaf
- f22517a056c2c2901f7b61f474d1b3b8af75a5417052b5e64181115672bd3078
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z0hWQ7I9UNZzbtNl3gf/ENmTaj8Ohsk8SvEiU9Gc8gYtK0mNxw4AY2THlurN18Z1Kaa82VLcsK5s2zWEEA9xBQ==