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
- ffbda79c05be779b6384d9b12bcdc5d6be231ccbc0187e7b8e05c8db9052ce93
- request
- 3eea16c0115ca232124a53568e16eda261cb0382b1085783119cb5d0269ae18a
- transaction
- 2d521b61f23bda6bf5a31b82a721e50017701183157ee04639b2facc5383612ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31430
the chainentry 31430
- sealed to the entry before
- 985017207f82fd75939876d41dd845bf5138352ad0c37f5d66132f1af5687f52
- this leaf
- 5823c38683128a9d57343fc55e28db78f01545fc735b79411ebff8bdd57b4a74
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ovfbYuQJ1bNOLeN4lpeYNEDW1i/LZddYQaqzNwunuab0DVeqvMayKIYN5TvPfOL84Ixoq/imX4JSb4YPAORBCA==