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
- 9028eaf8cc1cb2f128442f7c569655460538770c72720e88759d3d29391b7e32
- request
- 0da2c2397f2ca9a862243bc9c3032c8da1dda494919588e1dd8a463e3c6701ae
- transaction
- ffc148c8b074916ef57b35024e4735f8ffd941508892bb3dc44172ec6b853220computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40185
the chainentry 40185
- sealed to the entry before
- 48dfb2535bc6a590e954ca7ef5eaf12feb5ba5496878f504e16c4607224c8a98
- this leaf
- 3537bdf037080558bf50c6d1ce7e90e88489ed19a8aa1081e6610bc049ce59f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U8ObJHFBg1e+gJ/QxyRUj3Ww4HscmwFos0lgDh4Csoc4Ehiia/Q9LEqkKnxyc1tiPg8mL/V8Bs2Vogyk1QIzCQ==