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
- 61b844ac552cdf1a55c9261c33129cd59392fb384ce5620b04f9fba31b4eec0c
- request
- a0c806f18c634fa59f902b45577c0543932f12daf422c4cf5224695ac37f7789
- transaction
- 1454092702630b614cc40626c1a26d2a8bf12d5fa88b947ef1725430cfcf3c00computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18604
the chainentry 18604
- sealed to the entry before
- 2585c08d56e8daf4f49c3de554efe7211e9e742709f6aec491ac532282f8e84c
- this leaf
- 361c64b59ae0a3b6ba09827133bfad05eade7d4f887ce53780e050400ab3d069
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v/xqiRk7pEsyAOXrenUxDDpxcq1/AHrmH8De1gtsguQX3nbBgQi1ROekgWtTxeEhi/aZ/1CW5khqNgLvvtejDA==