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
- aea6609cda105c0e7a83fa06d9f53fe421bc7005b01bbbaec7efe216bab3e3ad
- request
- b467761790453aa1cae283d72ba96b5d3b196de1a8094a3b0b414c67bb4bf21f
- transaction
- b789ee6d6700b204de648d9c65f4503e2e3e4eecb3f24dee440eb1fd36fc678bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39512
the chainentry 39512
- sealed to the entry before
- 33bf6ac4ce243d33b1deaf6b856d931fd33c3e2d69b0e396674156ea92a900a3
- this leaf
- 80b6e13f7af16bdeca08d462d52dc19df2b1cef7f3f33cd1bf4ee29d0fd5d304
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l307uu2T7KEKTvPQutEtG2C92F00iQmAxyivBM5fAZT7f5QVWu4XTVIpvdxA9iaI8NXWST+5Dc6lptzFF8MoAg==