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
- 4cf26d1099bfbe02b71a301cb90a48079d66e62c4fd942f2b89284f69a7afba6
- request
- 364c6aa20ae5c003c928a7e4302d01f43d219ec8cb65677c51780420d3d61f9d
- transaction
- 2141475f1482318cd87b87dcb3881b16c374352e0e539eec7e512f554a3ea075computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56569
the chainentry 56569
- sealed to the entry before
- e2673a80aea8f7b357d18b3217b2d034327d231370f127767a1c26fac4dfd02b
- this leaf
- fd005ccaade01b3311263b18f1f2578e6f8fcc147037c4eafc8325d6cdc26b0b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fANRTBuJFmKmKx2NGRGAAmbbBLzHIxHqQJE+DZ5aC+rE2j9qXWG8smixceCPbilHXgou8HpDkWsVCyTLVC9fAg==