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
- 5b17e486b3041ade4c2aa509c1692602c2af1b499c15c6f67cf376ac7fae66d3
- request
- 11e52e0c704fc138b364cfc7c76fffbe0574da21313e29ba187786d9968722a0
- transaction
- 1daf4414457e57b74e05426ef9a62e7277b372c88d87833127714a1f74993bd1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45516
the chainentry 45516
- sealed to the entry before
- d807e3c9ed5bc298e22c2eb26f893b59b3d29cef752e48c5bfe6c59b67a318a3
- this leaf
- 7aced7f89cf1d177db8e12cdc60f0cfca50d6012252dba62e13178ee6dc0f1e3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +dhA2+5dJ030qY6m+5iDXEL75SZtArk0x1bv9LJ4rHKou5XkF4B2Fq7mlt9Pb3IzSbuaxaeFZQr8KljaGe02Dg==