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
- d4c38a72777e0edebdb4e85fb15be951fd967de0d47b35f8dbbcd678f44fc916
- request
- 61d0beb974a4e7944037bc169d3cdd712770b8094fa20c34b97e34c0d27c8cbf
- transaction
- 8c3089e08f2539707b5bc2508ce8568b3405d46709ff3caff3b6e7930e2884e4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76272
the chainentry 76272
- sealed to the entry before
- 49aabc220895e59db3f7b096a4c143a4d940f280a1ad41dff4406317e1a9c1e1
- this leaf
- b7af8ba89218b27ad421c1c86664c8da1bb2a22eed305f055ea5e6a164f51fac
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NBd19Pde7EeZ1A8K4DDgxLYFhPK203036Ob9b8FYC9bRJnp2EGwjxokSrIWqZMVvWheG+Bs3w35t6WKMCc+bCQ==