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
- 9375e5f465682a151ae2697999b6e8a434f906c9011d0d83e0f6bc6d929e13f4
- request
- 3c2694219994c8f6cc06bec3689598e81a3ba8f1dac545e76831242b247af1bd
- transaction
- 576d2876a6b90f6d7ddbead904b22c6328953d6fed8ffe55f0861e22f92bec99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64943
the chainentry 64943
- sealed to the entry before
- 8c9972cb7139c804f6c4011392eb855a105873d1d12fcc574d997d157f531940
- this leaf
- 8e62d9da5cb623f7b703478758200289be89d0d2254c334b1033969580083f13
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1/oXadryhUWkR1I34AWHt8QypkHPDk7Jph+GsHJcedJsIymkShU1rwHPVgqXpfc2eCjK27WpH884B11RtMsdCw==