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
- ec4263c52ba39655b379af4b210b555148e4cd5a47f48bad17b500dd54c57bb0
- request
- b1c9d1e3c993557b687b7394291dd1ee96454890f6b98e53a3a34281db022dcd
- transaction
- 04b6e085c487b470aee963c8e81d896c3db7679d91eae1cb6064407d397e654ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48473
the chainentry 48473
- sealed to the entry before
- 7b15c903dba41530fdc117235016e68abaed74441bfa17a9fc6fb7de59ee7dd9
- this leaf
- d4c6ee1557b134c2961d9c260108ed6c096a892cfd517dfb1797e5a4ca049861
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- npFgOMNutP4A784rch5VTQEOwmvytmRW1aFkWDi5Qae4I32vTnZ09cAnXdN6Z/p534GXGE6G5DTtTU7EyMXqDg==