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
- 7e202f49f65fc909d735b5d5fbdc930d7d1bfa8d998ebbd68361718049f4e21f
- request
- 5716c52c299c47c5048a971fac17cb588c407c2c5bfefcccf30ca0d6215168ae
- transaction
- 05d485555ab159d5b8402cf6ede681ff85873f7e71b19941a9185d1e2a189af9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69969
the chainentry 69969
- sealed to the entry before
- 0d7eed744e7142d4a579bbd67d305a1d397aa98d7bce69eb6f6b9597464a4551
- this leaf
- c8a101f63759d20cf2d8b44d0f40b448c9f56834d371943d112e098c0bf83173
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WJZE3vyofbsnHk5xA/d0Eb6MlBr7hsRd3Ra4OdbyFDBptF7sRmvFW2faxd9qX+9w9KgLjyzvkkZNzUfcInp3AA==