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
- d7eb2dd8a5a377480dc32343807229b74da65e357e8b8476628a34b63df75243
- request
- d85b3878bbd311318b6766abd52c3be29859f876d9e245ec125f60a61d4ffe8e
- transaction
- 691d6e4309cc43aa10c998ff211e3304e26022e4ee0bfe424e7e5bb969c78834computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40733
the chainentry 40733
- sealed to the entry before
- 77d86d6aee6fe032e33f842dcb760dd887cdbb8c8c78adb70eb380fe64809185
- this leaf
- c6a08820c09bedabcd2a06c948dd33d2208c3c3f16a375795985bfbddeb3b17f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sUvdiJ6PUv61YNTDRdk3VqObYYalTcvXs3P4h0+fihnH2a0zICDiyXHF9fg0lSbJBzdtT2UlT8K5nXis3PfnDA==