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
- b4ba7eda3836eb09b9043ca19e6e66bf211843cd45f2b4b77add0c7ad8f24092
- request
- bc279fbaf0fe8bea0317fadf73f90a2ff79b2e960b402dc2e966f9ce02310564
- transaction
- 6892f0e3fc9bb62d05f0013c2eb976cae3b38c0a39b04378bfd998ac0f7850bacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10344
the chainentry 10344
- sealed to the entry before
- ec60e5a5c7b28ad27f372b63e01ff018f2f129db48b7a136ee2ef7b29a848725
- this leaf
- 25b1a58e5e74da3ea5021647431967c4395f72131fc374f0da2344c375fc2809
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Kc95uMa9NSA1iYnpuqmEgzBNFtGP6IYoj3Q8L0lkhahNx8bXAb70m/rgxJOkJWvICF/N3kx7Ve2LP4ghCimICA==