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
- 2976fe1921c1810708cf9f403685d927860efe95df740775f43b5949e75bdc3f
- request
- 6f0c01689c68edfa1eb94c96eb2a542339fbc75e0f01b13a9257a5bd05996e2e
- transaction
- 7f55cb3d60f6cb003fc0640575f380b89ff24da637a399b4c6f5fd1e49818544computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31626
the chainentry 31626
- sealed to the entry before
- 976fe44a74f4f1929fca1b82c554493676d60528d5b7c37a6d05a6fb40cd9585
- this leaf
- 549939c8a43bf4dc5d029b130fd3d73ef25757212ef64237adc54a83d56ae095
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Us5GHxggvM7wLABElmAcA/IIJA79EkVeG+WMsoe1DO/iMpJqBxbmQ+NkVMgb3SsWIHBVEjs+o9j3PU/tDtc6DA==