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
- 7e569275460e043aa234176c1e83fb44185773cef666d969a301bedb20b6294f
- request
- b010db2a19693cb7b472396f786e4c2ce901d0f5b77575756098b0d56dcbedc6
- transaction
- 1f603697af25539c72970ae04193d6734e9e3fc80c929c04a7042adfbf2ec748computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46960
the chainentry 46960
- sealed to the entry before
- afeea5a64a4deded52d0192bd5543d02c878e2a59f9a8f28b191ed3d92c7f5da
- this leaf
- 394e17ba6f2eb45769b548089199e359c0e91dd55cb196ce8dbded13d493640f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mVlckxArgXucuUElr0R3movoHVt/tYkUmGkdt/DkVnfex0SSpdhmHjWMeYPxz5C4lblOL0D8QGw6yH8V+F8iDA==