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
- cac83eeecf667f4ef29e8eb3598d79f562469e60fe61c48226310f81d41819fa
- request
- 8fd5e29a485c1a16f6b444c912bea2ba10627be496beba7cfd64b9a1f97e792b
- transaction
- 8d2ac87d62d3835ff24dcc7e7514e510d8f5210d843100486a6ba08fd1e47b24computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37749
the chainentry 37749
- sealed to the entry before
- 04b099584751702b82837604d2734618645820928e2e9876c6e53a4d068e399c
- this leaf
- 3544000a023666bb195096a43f120018c564d9d6c38117fdb47e7f75d6b537bc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vHypPdlUYr84bRdNL6TRL/BmeYosRfBm4uTvJAVCUJNtT8ggevZdC9rgMAmryWeYmoSL5vvBe8HeP1EO7BslDA==