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
- 297b00acafb00a7e224dbe37e2a3f1b9b885deb8f648769c0e7996434002c8ad
- request
- df2fcf4999ff15357d28a0688b0c64d15bb2f6ecbbff79923d68928d74695cbf
- transaction
- 4033fb15c334ae12419a410dad43642e4c4218fcf805583253fa6aacc7b868bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44186
the chainentry 44186
- sealed to the entry before
- 7d036c9487651ad3caf90cf1f6be2c9be9adef873f4bfc0665967d8a5378bf86
- this leaf
- c76e4dd8456632a49bdb2aac67224ac8009cbc2a1e13c5e307bf6412cb5b6e57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RjBVaKz+7An47CMJtAPtsdWNO9ameYCuLqrek61rxof7D3td0oUzGHHp3ZGAZ0rNWTngIKnGGDMJ/Zo03agyAw==