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
- 83c1bc049945db436e193fda2e40cabcd3817c4c289bdd14777b886168c2fca2
- request
- 49e8d6fdbf20a746046f62d86bdcd290a84c1595ef30e36824d3c2313834d101
- transaction
- e2f374b017ec42c9bf4771b6864aeb297979dff23afe81cdac23b304f5b1d1d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20139
the chainentry 20139
- sealed to the entry before
- f6fdf6d9f74c7942d4413c70b19c7c7a81446f31230fdbc59fea1d7f4df43005
- this leaf
- a82df8bff1105a122a362b8b603a5f74a5c6b947869b61994b8bed9ec78de6d2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8lDpezIoOJ7t1xm7niGU/U5pkgTLVxP17WOlcXtRGUfennNyChFpeomlFwVAh4b0r5GD1wfFCaGYgdYBysDhCQ==