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
- 0f930a3f857a7c2624ed21af7a72ebc254dcfb5c26ec689919bc658f9c0201d1
- request
- 43f72778c4fe5f47526cb62da74da59bff2c08e14f4674b4bec6869c3407d70a
- transaction
- b7be50435f621085bec701f4f97411d11f0fbd626c1c010303e34133deeac650computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17204
the chainentry 17204
- sealed to the entry before
- 2887986db3b1e1c1aff5d71f6a9fdfdae647ac1ef8d2968b62e0b437f813c913
- this leaf
- 999a00f559822256340ebcaaca241cdc1abefd81ad4978b36d6213def0cad038
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jVFAu9TPFgZZSInxNxD4wl4zR9u43hgPNt8QExe97C/4vbIVo2gPM2+Xi7Dq7abAsH2kzBmwFP6DSqNKt49bBQ==