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
- 4e3fa749401492a6cb87648d67c5e69d44770f3d78e3de8ecad82ce708179dc3
- request
- e3d525f5821ad2472be8fe555beae543f954786204a18af3ea6f27c0cee0bfbf
- transaction
- bc642a4e5aac53dd9ddbf08c64f20ab38601d8347ff9d68ee5641dce312f74d9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3046
the chainentry 3046
- sealed to the entry before
- 543a147a95f3fbc652516685d29a6e253853a5cdcc1144c32f5b1d9d4412f306
- this leaf
- 8df9dc551f4d6455e1b3af7c1a7f102751067fc02a4c5e0a7be0360e7308e4dd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fWYw302+iGRkc2vj5T/DAS5+qahAkFiYfeJ8Slu72iaOsEwBaySqePByX5Im4Ai++32DL03UWmcEeI5yWJzlBw==