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
- 30e30c258030aa442630194d12bf1acd5b268f980c7403d97b1c0f305c79d43e
- request
- 085b6b9630b9ee965f17e144c7e02029abd99eff673c549884595ec6218687ca
- transaction
- be98cff98634d61c901959b66ee71eadda8cc3ecb52d820993173aa5fa6ebc92computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31033
the chainentry 31033
- sealed to the entry before
- 1f2d5b5ce38b78726ce57ddf3f45c11bf5b786a7229e9094d7d3900f990dcb75
- this leaf
- 72580e29da5d40fa3f2358174b73f84c42fab76219ab375697995226274cbf2f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ikbAotMRqqzIeu2aoAV0ZGBLIvnJo2zZcTJtFnDOiOOAY/rNKHluCqvEExpqJBk6Gt4kGiqR60IozunCMX+tCg==