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
- 7624a72c62e8a685db404bd864a51ddb96aebba91aace2464592134055f5ffde
- request
- 0470ad911fc5369307207a2e8201641baf41e4fa2287c855b29c2c0cae703154
- transaction
- 4902832de7e1e6d52da842d93433d8304cc66536b9c70e8081b4122ea3d6713dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11412
the chainentry 11412
- sealed to the entry before
- 54142248a13cc12972d2b2a67c4be5fc5838aa81185f9fae7b176a65dfbc82c4
- this leaf
- a3426056e261eb6e13d6739b780ad0c7e58c3d28a20957ac8cbde02c3ca51335
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5JwfwhDI9bcuR3P1PhBY/k7gEn+GD4m2k290anqH+GKP5lnyr4LfEkUIb3Gbna/qXgYagpS8bWXDM8PwH1fdBw==