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
- 0faf7ab57018b3cb3c184e25f181564dbe21b4a3298826dc6678e4980bb6aaa0
- request
- 1505d3f771aba15e53b7402e63b4d44c43d5ef707a0886b329db3043149ac61b
- transaction
- e4418055f2bad09c1400cc7926460c8c0ecad8db14db009ae5c228b32e1e826acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25022
the chainentry 25022
- sealed to the entry before
- 38edacdc45db6c9455bc0b03953bcd8098991cc687d6dd169b35da6edf85498e
- this leaf
- 8b476f4cc40f16c2a9fcb5d7afe82014262dfdc4f23d1d5ec1c70fa7a0b5d913
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LHn5fNkl0h6aHNCKikoueVWensE4x5uiUb+z5hfVwvDzdyA9zzQwgC33qM0cbmAyH0ZgedDsNiLig5xt5QWFCQ==