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
- 65598b486c2cd86efa9440056eb651c0c07478a9ed1a63ca034a588a4ddeabbf
- request
- 840cd8ee99f5957e07265dec4d8137a09c2c4cbe95d600417772fe6ad8135e39
- transaction
- 9900ac11dbf6292a7d7fde952b508b86f59a6b7ebc22bf1eeaf6f79a2b243138computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22692
the chainentry 22692
- sealed to the entry before
- cb0d77622dd08fd904e5ca29ff0100d80365dcd402feaa26fe3efe21b7f09e18
- this leaf
- 4a4910232be495ea36df281b21fc1cfa047f73213fac41ce38dac3c4f6b5353f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YAmmBTG88FTYTThHndyxEW6msytcnlgVYsv/XuovyXas1ytoYVf+fer/w3U7NbsfUD4i6w8hh94Ly5xf35caBA==