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
- a01813ea98c2a50116a0f24e4dde211a63e5293f786ec65345b2718b5db55821
- request
- 78e564c0dab70703b5cae3d83ede6a2bd94cda72350130b5e9faf03389277710
- transaction
- f70b365e4ad72c03915a206b313e6dc5a7fdf9ef513763075e34726d417482a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63520
the chainentry 63520
- sealed to the entry before
- 2e3f165be59f1fa7983d88d05a4c05d5e2cce6f9c32f463fde6b9f0d17c210e4
- this leaf
- 9412f98d5cd6d462f22b5a89aa886a7866c2d80cd5ae4dfe23eca71b0193b379
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yVBAiNyAagEvRiAhOJ8Fl+67BtX4GRKdu8vDeePHpK52gfwujlx/0rICiK1Q++W0CdqkI60Qw2yDvPbq7nrNCg==