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
- 0506d9e319b12212cdf2e46fc27a1f621ba5f6e003a98d5f3ea3081a9f400945
- request
- f1c8dc6d76e5f9141a240be7d9e17d5502fcffba22d9c5dd2ad5449ebddce2cb
- transaction
- 73267d4f34b68b4bf1b3bc4fa3eb625b8c02dd74a356121e80b4f62795806530computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33974
the chainentry 33974
- sealed to the entry before
- 40f904b72f9fbd5b381f68829105f1f391ecbcd1a8d96ae14d64eed69637e4c0
- this leaf
- 82e0b5ac6049cd44755bf2f49d820daf6de28067fd2902a9a13b26aa73be2881
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c562XOZR5xQ4pE6pjbNNU2aR4Z2h+uZ/RNlLlp6OjC4qvOYde+SFGrpghWziI0W1pExYPeSw8+xsh9XpCNiABA==