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
- 8ee5f2e91aa4424d8327f9e8186cb859a8cab4e274d103c37a0f400ab14fb510
- request
- e1fa979627d68d6792c80ca3d59d775fe773a4388a21fcacfd702c911bd6695a
- transaction
- d6edae021607b2d1c669c51223051f3a206d0cca37684b413bfe09dff0bdf02ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51155
the chainentry 51155
- sealed to the entry before
- d206f4ca16e92eb2ac7e46c5d7c352e6f08454e729486177c5ec4f7dc2565a87
- this leaf
- 471a9aae3290b8c8ae02aa31fe607cd6c23eb5d0d059d932bfd8405f697cd510
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ogo/Wj9lnnSscrJL3EhZmCdgVtYsqxZfOGqUVrWElXXcy4HCU6G0KX2AGrYprN+Esruv6Qn3qkwE65T01a8GBA==