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
- 30b9646d5088f91888668562ae6383998b3c3133a7ff2db3ecd93cc13e7fef78
- request
- 91e9b9421805366a08424c7448165fdf752c59b743becb3ae47be532436e61c4
- transaction
- 670eaf01f09f6f16ef3800cd8bcc358418161430b3b067b1f0642bf378594d35computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55187
the chainentry 55187
- sealed to the entry before
- 0adf16e0968286c6b37c9637f45bc14cd6820b871aaac5a0ea6a54097a96c529
- this leaf
- cbb3aeeeac32649d7bc65fa9925f028e9f4402cca1f4dbe444781004e50b98b6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eSo5zbAtJM2+No1pl83/S38x61X6GBcNIGtK/OEC5xlFNscOvDsZPcGy65cCQdU7dtkttUQRGJnQd15YrGYxAA==