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
- 19a8d37b927e40a4ec4de0101e7fc39e469a417456b3c72aa7cf8dba8f6d8764
- request
- 120802c115fdf8978a26232eb9156e857835a1439851f97745609874a89b7c87
- transaction
- f6e565e5c6ed9be1028e497b12c6b9778dd324246ac9e6ce4245d595689b45eacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55350
the chainentry 55350
- sealed to the entry before
- 712f6e55d75bed3d153a8cbf5d0251d5273490cbcf854d3005fbf0baea9a1007
- this leaf
- d5fb18f2e54ced25ff237685f30bcd6a1ecf02aedeeee6f43b2237d01327235c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Hqj4ZxSLax3dYbFcM5IC8UDSKmDun02i3n5KgLCqg4ZUtXUBcPbsAuU7coVrAFnkoxKzLWH0Zc1S1cMZgoJjDA==