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
- 38ec8122ffe71288be264127c9a32d6651a4ef155cc44cb2b7449432cb16db4d
- request
- d10f7c9fcd03882032d36d019ab3204f9fa7bc9c2c1c111cb2b85e40eaa478f7
- transaction
- 806d7aedd733b8fa5a608ba296b5a54154cd9e9276908f629dfaf1bdf5c0928ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16020
the chainentry 16020
- sealed to the entry before
- 4a3a9fe0744eb3a0f7da80c6ebdb46a3c92eac74b61c7ac0e8ce384cd4169da0
- this leaf
- 69cd01b4664b593c022470ede2bd1cf41ad0592cfcd6af9a02b2c00cb3653bbd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DtNfEVJ4egeqBKJ6KVj1P8BkCbbrSc4gzjxQ8tIE1naSAfPWInOBf1MbwdtB48LYKQA7HWrTagj6ukJGWexcCg==