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
- 47d25a1a36e874d9d5c1feaf77070f0e2fcfde88201286c8f07f64e5e97b46e0
- request
- 7db40e3ecc65675e417b763f46d94aaa9698be4599ada883738218f698c97ed5
- transaction
- 4f4f966bf408c3a66ac7331c89129a525b3c27f3d2f64176178356d0bbe254a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71886
the chainentry 71886
- sealed to the entry before
- fb0be7ef2e11a3028e01c0371ada190f7811198cd7e9469047fe30a0373d1542
- this leaf
- ef543fe5822f1e4a3f45489000b280350c02024fd63008f89c24df69377c06c7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v6HM72IzFsKeu+wb1bDz+iUXtUlOrjiam771aKp8kFd1hl7GXElsvAWb1MprPx9U02jT7ueA9cUFuTsqqQ5nBA==