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
- fc9a3ab6cf8778bad6474d088cf7a08096149502f30e07e5b0e856e642577894
- request
- 7be7e4fbea0e9cf8e4e4769daeb35ef34de23a5272f43c171ec03ef85e40b330
- transaction
- a68722718b68829a836db782d41bf2aa8caeeca4c504f56eae2bf65c0206e020computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23590
the chainentry 23590
- sealed to the entry before
- c154ce8cee92740f181b7d63f9241ed70f760eeea2a8deb9897f773a6db06caa
- this leaf
- 454c4378b80bca65c213366cf1532ae7d8e30e56bb3eb05617ced6cb7fcf0037
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kmOYUM71kMLIJttEBK1Cq9uNk3VYh/XsGwh6NCdaSdcK8YUVbXgA/TeeHmADZq7PvtHj7Vq3pakkCx5aLbgvCw==