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
- 4782f38771930d1841a79cc6ba7becbb0d21e6fc21f566220155feda006ddaf3
- request
- 7ffad3a0da37aba6da73295d9bad02ab27819675810d53a3152efc6fafecb438
- transaction
- 216efe4f00d14b2638f1cd432ad5450aaf323dff339b5f1c61114f5170a31a68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21405
the chainentry 21405
- sealed to the entry before
- 668a81b3401ed1179e1ea6eae1660922b6e2a4fb35d8d6f5e20cae33a000ce05
- this leaf
- 9d5920d317512dc5a9adb9eaa89d1aa5d2388d0f2dca613f3d2d9b3af0fbe623
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ql9wW+TZOmIARHNbhlaeVy7iQQMmRk3F5C8RvEtJpYDepDdEf6EoBdjcgsCjbvRX+obGYuSuefY7WsEhaZMqCA==