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
- cb06454cf3d6150088ccd95b6a3100c71fac2ceebc93ffbd58f81ea7c16bd73c
- request
- 074f14328f48582da5db97382040a612b3d57bc79afe5a29072ddc172358b13d
- transaction
- 8a1e7de7bdca099ddaa658d4be5b2692a4b26e40e264c1356869005f50f1f495computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36842
the chainentry 36842
- sealed to the entry before
- 4cc6823622663028c8afb6b31b3beee1b6ab63364079ee7d119f8b70552b5dd4
- this leaf
- 265aeb731721084c994e53ba5aea437c33047fb88dbd64f3121ca5ab5a736178
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- p16barXTcapwq1rrSBCBucUOoyxFAscXkxbybduVH7KdCI/4588nGBjpssbWK+EFUQi7934gz1Xitpiw/TBPCQ==