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
- c32913d8c43304b2676c8a7b12970ca14c6e04273dbfc3437cd6e429c79044ce
- request
- 558d649376c89302721809837d38a03d086cfed4d2fe57d55ed6f6f34b074858
- transaction
- 5aee291b04f89df96ab852b81a48e834e814c95a126c876253d2d48f08a36a2ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35369
the chainentry 35369
- sealed to the entry before
- 9250fceb3d4c72fb8f6a38687819cad1cc487711ad075c4409eb5d5f0bfc96c0
- this leaf
- d814fae8b2993322100f03644990b07ae31a9af45c1d6a57312ea17a4a56006e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7WfBO/583tn26opjMFO0EG5oi4j3+sMXmRIJi4n2b4qaEIpFE0AhycI0Qpg2ck57Wuz1PNVsWr9BvMYTyIJCCg==