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
- 54d60aeba8469fdfa0cefb9f97191380fb8224fbda7f8b1a6b16dba74e42cd28
- request
- 21199b8a05dbb723d4fd67a3a3d1790ce0c978e0ae5604aa579377cee77375bf
- transaction
- 107daabb76c0b21b7ac045fa20816255ba013a0ffdb5fa44ac096cbd1bae485ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 631
the chainentry 631
- sealed to the entry before
- a751c79b31e5aaf49ba28482421688d1d127faa5921de3a79b6d3d53f9a45a18
- this leaf
- 224c87d9c43505837fd0fd6da7cbb1bc750a6e14ccc79a2ddbb69f0bc635981b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9GM/K0TtRm3yz01Afi51aMzznsTjPpJSJgQxl7POsLAhR3pc3Dz/DAMtFNits+9mfCTyle0DwJYDR3EzYTWjAw==