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
- 9a59bbf56683033ae7fae0e79ea2798faa4d12171e9df24d8b8dafd37acc1876
- request
- 56ce80caea9002c3b675437806e98ffb68c67834cef814fde9270b8b507349a7
- transaction
- 02861cb3fead66b09c7390969022652b3c042ed08ed1d37fb7c4f230b6bb92ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77011
the chainentry 77011
- sealed to the entry before
- 3d3740497acd74ad2640a676702b50ae6e1b784aafae455ad3adc68dedc41cbc
- this leaf
- 614140a07fa3d909d95922b01507dd6d5916aca39ef1bf8fe362da38f8571789
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VS0u/Sx/4yJ0AxzipjqiWIR0Nh0ugy6OdIJG/3Nysr6+u4QraIzGkToTj2LQeXLhLrky0G9QBNSxWvk1vvM3Ag==