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
- ea61fd659033ac87892226de1c73211a1a717c535e2e63ee163fe9b6b3b329fa
- request
- d8d2c4da0e86a07ec302f51f9f0a84b32907bc29f183d896d3c3cb354ba6dbb8
- transaction
- 8c040c83efe869be1dd97c89e534d0ac9686e74e612e200de5a34e99a9aa6e11computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62535
the chainentry 62535
- sealed to the entry before
- 00d5625274021381db05256fb408ef74f43c354bb1c66ee105b7e4f66a08e6d6
- this leaf
- 812242e7370ab443485bd2d80a2c870c63aaf673325363b1ca20765b0e96a673
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O36jJlQKyVr/KJDYu59cxZYQWiSIjOspstzj+zGwNtwGPki8ESd9GtdFiQXAFxi/UBA/SjV9ecYEIAOHUvIDAg==