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
- bce509338d44fa2d955e76b8c54df8305cc04f6af4e22e06cbc929d3c45ce182
- request
- 2eb3bd970f528a87427cea0085ce28b43588914ce2504ad0297732cce23b24f2
- transaction
- d71be7c453328dcc6d7e760e6e192df5b2e9638d3d95081a33074f01ef3049e7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72126
the chainentry 72126
- sealed to the entry before
- 0c1d375bf07126a4307d509a551bd1548b674edff27adad13442bb4973b88d82
- this leaf
- 4400208bde3c8ae4204623974a974ec76da10c208509f0725981903b091d05d0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7U5n+rgKXVZ7KMKG/E7g6uCmT+bSfbiTzYhXsEiuPUL9O9PrXCZYzaCb3WAQ9zHvCzH+pP8PkkO7D/H3svafBg==