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
- f48bbcf469a1e096b88eed303fbbb8ecc15566defa4b88c7839b488be1642cc7
- request
- 872365ae89a5deaff733a848e0c5cdaa6e63e66efab084501e4c58ff0806889e
- transaction
- 59d9aaa4beb043e3591cae4c4169c60c150ab347338cce89cc6a6a1768c34f8dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59654
the chainentry 59654
- sealed to the entry before
- 090efac5f523cc2a8937b0efef706dab663fea0ba33441d173cc8da942788953
- this leaf
- 9312a459faf4153348f1d8f646810c80fc74560844b5ed2b67bc644cce231dad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VcBqB7I/xBQkoi5T/F8tVMk0OGHcIqKiT4kOPIQkZSuf95sdULCNgqgHpmrkP8lWHSyWkEBwnXM+DHyPWCBUAg==