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
- f32b9877c6de19314e710c4dba7c906ebcbc4eb50286054232cce34ffb450c4a
- request
- e66f0051e8b2c473c0600096f9b7019559a48b9c0c6ca83a101fc282c71fe5fb
- transaction
- fcc1c2f849aa742f14a1390659e76d9042f664bcbc5df837f6c9f61fe5c9625bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38180
the chainentry 38180
- sealed to the entry before
- 37a275196132328e399c2fcfd5a0a32ee0a4c6dd21a84c437644e10ca3c28965
- this leaf
- 75aa662f0f032c844f493705e65bddb26207fb303883fb7b1861cc68989ae171
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6favoy8+OuYnVAJAQw5xxy3DDVfbobuILY4ZQ7/Ds8XjW1N/0gHCUoCa5Gkev3OpvhRJJ0hHtKXmBoPvdsjPBg==