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
- d3b420ddeea98f45b8a52f0a3ddf10e7055eefec597a471731fa443863f9eab8
- request
- aa14b88a1ca6371ab90ea7483ac9561d3c6440902d2e77ef6f953ae41f7e1aea
- transaction
- d42eb1d8dff7c77ec5268a520dde48d66be855af8b03d9f5a30ca3b46d877a74computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19362
the chainentry 19362
- sealed to the entry before
- d72267e103a6e9e30a5f1de2059baa68403f372431ddccd7e5f8d89689009c39
- this leaf
- 509cb3109f2470ef213f8dd90b8524c83e2e9eb6d972f84d35ade6a3086001e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3BAbh4bUvTc6MSqCMUdd0xJBwwaXS0IhxPuOyKO9/x1UBscB+RvQLdBCNxzZTKmM7g/TY4NnQoMM/zRg3520Aw==