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
- 12e4ca7170096906eb60d77a0959b6d3db6198b21a10a5b037e3e85c276ac167
- request
- 00bcc082fc72d6164e07ba138ceebb35bf45216277e3807c9aa7b00975f95d2b
- transaction
- 6e28a42e653d8fd42c80460d9181cdf7add830f3ccacc586071d0889de435c08computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45208
the chainentry 45208
- sealed to the entry before
- d2e1ed06287650b33c67fa2675bce2036024c9c2599ad7e51f08a04114a4f393
- this leaf
- 1aaa189326b668fe05ddae2aad8ed762e9d3cfda93fe71a65ca84fb1f7c49c60
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ewDCe21p37+DV9Oo4FvFdQNUWIYlJy7TLWDCiBn8DN24q95Up7144SSYXnLxyNamPqqh+g/X41NrUXJPDQ0ACg==