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
- 0ca528c35a2670806f393cb9e3ae48196e990e390e13186f0005502960de6ce0
- request
- 2d56ad54a39840d593756de01490e33a5561e293bd450e7516526f02351743bf
- transaction
- bcb107e57fe8c5910f02ecb29cf446a6e065fafdb62dbc90dd5a75fce986a682computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73406
the chainentry 73406
- sealed to the entry before
- 50faf28c8efc16561f5e712207a8f169f5b4578fb83e25742aaab8ec04252590
- this leaf
- d6395b229645d9f3983b1c398b62268c87a560f54d8edf40071e77d46d55b1ac
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- r2Ijs88jLglmoRYeGRrZ1W3y12c9TOaOSgvEJBt91oCSIkjK217kW7IVRyI1hh8J2i1GxplD5+kgi/JhDQQWDA==