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
- 99e2d17ce4469dd843e36fd14302cc870698c9eab8f4f21846ff93f93f020f32
- request
- f1ed41b1169a407a7739aa739793285ef40cea51d7400dd603628283cb48bd65
- transaction
- 9aad77d582e8fd8f96328796454000f9051a07340f2172a7c9bb5c040cae51c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60356
the chainentry 60356
- sealed to the entry before
- d992654194f296b04709166b28c244a0e4960c20daf35677f255046368d9723b
- this leaf
- 4b81efd90515205d824efe1881b164142dc7947f2024c8a59941289ff5a707a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MZGOBI5ofgqjAhV/9IqXUCotABXvHcMyULFEyEQjYMwrAgQ8EV3WXfrvwcEmvK2EzqkTqFxGT4pT4WpUozMKAw==