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
- 5b339e76f7ab295978c163edb97add9bfad9c823c7e72c0b5df4ad921ed9c4a2
- request
- a94a53114a05b193299789c6792931d13baacbfc0e9d595bb74ef6446cdfc457
- transaction
- 6cecb71694479b57b62eaebb37aa5e979907443cfaca2d74308c80edec0c670ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35731
the chainentry 35731
- sealed to the entry before
- 393aca3e7488abb4ad5594c7cbe8baf21e115b2c8dc423be655a7879824e40a3
- this leaf
- 69a50646b1a35e82177434ff8b0ed8fb485b2657cc39f84d6020a29469e49d65
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BZYkwnJaWnwvr9EcAf1DAhZXPYs8iE5R1qZs8z4yIbn0mvgGMod0Tu8O9GrvYGom0a9oNFpDaeZD2O8VAiM1AA==