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
- 3511acc356c460a1ce71364d305052d25acf4b9ae04ce860b3c7fb931b55741b
- request
- 3cb8c3922e8d532809f0e8bc0100ff9d1468cffe05421daaf4eb7723c9ebdfa0
- transaction
- 9f1fddd0bf84587d36e8d28fb925a3b0265b7777264f8b11ffdabc4111556854computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60920
the chainentry 60920
- sealed to the entry before
- ed314505f280f74b90a4e11de7047343e8019b75eacc92c9f3f4840c9d790588
- this leaf
- 8ac2560553ebf90b7e139996cffb39ac02fcc419a3d71f7cd4a8066e0f135a33
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s2gvQDmO++y31rixhbe302z1pzkaPDMG1d5PLahpibMgO6mbiCPBk0l+Z7ar86K8HLRpDIw1J1jgjmEA3MvSAg==