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
- 73f954aebf41a5fa2323c8011e4427abbd5c563443d3db6b67ba60f5a5472e19
- request
- 737990c3a088e6a81b2b4d5ae6690a43322cdc7203464f53c59deace072e29e5
- transaction
- 4b4162196d8dd68b5ab837328169679937bce0fdede3af432d65aa3da5d608decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33450
the chainentry 33450
- sealed to the entry before
- 94733dcfd388f8fd76123da9978afc853d6ba4125e9f290c48d1130a107bee4d
- this leaf
- 1ccd9d0543fe0d2b4611ba3022c9c4925dc3845e4c301d4c6b09722364a681cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kwmPbDOTHTHWpBIS6K3dIjO3a41+OCBBveFI5JlT9cWF8vSMn7RFilAechnZtIDsTbs8pAynzud5IowMm+LwCQ==