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
- d170b3bb071363154c5fc0786f72d7a4688023d9d4afa134a5c3ac3970c9974c
- request
- 9620b0380682de9bf2ecf553e578eb2625ca706865ee6e251a72455d9f189db5
- transaction
- 5808e379c856353c93ed7ff82bea170c30b6c768f31f14d3e793952ad69b5890computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46019
the chainentry 46019
- sealed to the entry before
- 7c3122f5daa0c3dc7694d6b4afb312d1a542ecce8045b8d7a36544eda072321a
- this leaf
- 2d69640922da8f9837442cc0d46387efc81d2a6e327a3855ec197e5aa5a6042e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0dn8JZHsqt7OEYEU1TK5dww8tInShgYuVh+OVV49XuqO/tjqQolyVMhL8lvR6Uf8ABRc7oYNN5p+F8xJR18KDg==