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
- f0e51ba777cc21e4a4a10375e2e2e5ca56dde4fe09049f1dd331116d776a0a14
- request
- 51b8fb678ba5b98052c7294ccdf2c2e9004a77926bfa191023e0c826f9303931
- transaction
- 96b6beb2155ebf07a1eec4a74e82bb85fa169055372ff12c86a7742aed8aaf0ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67342
the chainentry 67342
- sealed to the entry before
- 93ad9559e35f18c9465082d2742d8f63d0f4ab6ac0533e483a4dc9293ed8607d
- this leaf
- 9ecc774f5df075c894ed8faf2a516dc334b0ec580d6a057efdf2c05b1140dbf8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UPpE6u0xtRQzl5+PM9lOJ1pADiruy6qmIQQAU5KnECLNF/YFWNlGrSnv5c2Dh63yzRAaslmYqzDatOW2qBR5Cw==