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
- 6175d079d8ef828284f08377a0e321e5dcbc2f301037488b9f6df9165859651b
- request
- d24af3ca83e79612e2359f46af72bda50bf52c8bb8a4c15788cc37987d71b21e
- transaction
- a1bcf3e08112e401d25100727b0c3ad12fb6b0cc2566237517043ded3b7f1cd5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43257
the chainentry 43257
- sealed to the entry before
- 0c8551b7d18548d16b9305edc60003dcdb4de103d5f70d32351f0b8120100a9a
- this leaf
- 107a1b3f7edb18734c94b99bd4703fd1c93a979a8fc837d6024145ac4f619709
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hXqDCTBvMmLuwPhep9x3vK9HTYs91U+Xu0UGS/9Uny6axMaRka1MLS07Z156oYX33P9sEZfPFaDl+rZX2n4lCA==