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
- 21728052732653ca4c985bd8114045eb1345cb70d05bae1e29d56f860f5a833d
- request
- 18e9adef9abd966063e599ff69c943ae6e05023082295118cf53b0aaf977f94d
- transaction
- 9528321199400f7cbd6ad0e1c3233d8ecc3b12d8358df15f7091368b9f1fb468computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45359
the chainentry 45359
- sealed to the entry before
- 01060cb1a8bd7e89e5733649b478b94e2e1ba9206b90689af798ac9c37b696e7
- this leaf
- c61d8a08bfc344190b88f7bfc474a19ca8bfa17cb5e88dca8de1b953a9fa460b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W/l4FySl7ezatXrS7KiRu/pCMEr8VI4QLmEvrp+ceSFvR5+XYvMxiNKcwmhle3Qsa8jjLZmckAYDWqRo5BW3Bw==