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
- 85f82e1b658ce3aa821f977abbb7c8d414baa6df012fc79070ab21da4cab05c4
- request
- 04fa936455999fa4ea4d9dfe1db3c93568dc12adb58ef7df3c45861b2c26c339
- transaction
- a6997643e13ad81dc444bbc33895a6083c57479d2e8eb63dff200ae0ca6ae7b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23447
the chainentry 23447
- sealed to the entry before
- 9a4a147dc90f3a8c551d7916d7ff326fe6f51ff232c90704d480653a939c236e
- this leaf
- 0cb0ffd2595c0cbfc2de9391fa36eba1f2be6f3cafe2b67fb8471a6485cc5257
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +507u1kN3D+xx5ov4bmAx9Ez8CYXUrbZ2VtbwsF8emlRCXrZRC2dXUdX9nUVKmektkuHxrHjgaLxOsBGIUG5Cw==