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
- 4b4bb72ed768257f1d4f2d09bf636cb5a7a6bb7d69f04949be4168f4f29cf8a5
- request
- 3951b75b49a4817a6885d4bd8c184044eabe2008c9a214ae40245554968ecb1f
- transaction
- 157f1f5ca6467d92b31b5fc5a969ce57278a67739aef8d6674608a53f8b542e2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6143
the chainentry 6143
- sealed to the entry before
- cec2215f781291c4395bc4bf252c9339ccfdc65a2798c6dae6d50c967dc9491a
- this leaf
- 6134677da611350a68c7cbe2721f29571c421907dcd541b707a7b293b0b818df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- H3D+jzu1oVClTasQ9Me51yAeGAyHspIkCINls1qpDJ4pQUTaX7o5xeYNxPou0x5TyxOX+mwOxVnB3rvGZ/2AAg==