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
- 5bef18451ac24e56b236934b23d1021a6eb9dd58017678d4efc12786829df6cd
- request
- 329d0952d5721d0e1bcaaa9f2bec1478a71c28dd655af12be2249ac00f9babfb
- transaction
- c6b51d00e5939faaa55c05c9142b35523a7e20503df76fb0d2658f53856f91cdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43884
the chainentry 43884
- sealed to the entry before
- 90905bb1e95d6a840b497078217e77e9d5072937feb59225bf9c50c45fd32ee2
- this leaf
- d381b046a192f164000bd2d95364bda61dcb0cc97467c73e97ce7e6020eb32d0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aTp+2JcdYK9GcIpbDfsLY5uWor5MPxQKhWvdt9Cif8L97zbSiuD9qXdOEYrOLoPRltVcaz9qs5TOTVHUQC+SAQ==