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
- cfda6ff4ce2590f4c695ae2dfe17141bfc2529abeae9c476b1797961bf2fdd53
- request
- 3220e0811872c1b82aff4f80b13bae35a3ad990cc865c57270663e9615cb080b
- transaction
- 425b07e9a9e70e172e85bf0500993de20939024d77d2fc46da93e78cd5d8bdd8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11814
the chainentry 11814
- sealed to the entry before
- 96eaae64bb544086bf782bc3195003ebeede3d8d78919cc71ab4ad182754f4d2
- this leaf
- fd7b0820fdd8882a2134a2ade138aa746dde89027f0e4d117e0b7ee7aa4b13f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VOVcUv89jXCRMd6nOVO69pJMVqBWW51gFYFbGm3Rws9euBnxT0kis5OrCw/fIc0GN9+VZKbUC2HqEtV80rCgCw==