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
- 45139aa8814cf2243751f840060d5eba92cc38be6f4284f5ededeec481035c4a
- request
- 8505e360b58f7204d13273b490eb17271228400a7fc68a5ae6bb9b5fd84b5e74
- transaction
- 26cb58c6edf8a00cf964a4e22711933c63ea2cc540aa8eb3ea72c48983ce4eedcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74264
the chainentry 74264
- sealed to the entry before
- 9993463f8c30774307142216eb8182a9deb29a2e736ae27a472e4bcfac7c903a
- this leaf
- 1ad56d3b65183ec598fd253a75bb04f5a6e1a24860a2a092cf16c185f8bccf9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7fq8slJvpgGvbS2TcwyoGLSKSbR0FVBUVVTwBuwZAKLKFGx74nzlouTHtFOP1+XlZOJ1e2tY7Il9CF28O7eMCw==