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
- 1908597857739dbf4ab7139143b1b9f815d3055f481ee66ce6a239bc551f68cf
- request
- 9212fac5e665a1e05f3933d77a6d01bc59cc4076315f395b535093c25e98adfc
- transaction
- bad2f8b764765749ac5686bdd678a54f7e40674efe90478194c3c07d112bcfb5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20744
the chainentry 20744
- sealed to the entry before
- dabd5428bc93282f2c02754843ad80689f8bc2a144c62a63cc2efcd535de41da
- this leaf
- fb70bcdf6b28615b12b3cc77ce47fade08f902fd94cee2868370c04b180f49be
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZMsNvzDybrTlHLNeE3NB5GGH5JgTsJKNHtxpgUeTLU7xJYL2KHUz1+IgeHFdVcHGbT5+QloFTxGcLkHzcz2ABg==