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
- c48285e6c5a7edc9ed1de0cb467ff6ad1d0173fcbc937df3a904f05783b4d0b0
- request
- 79d01a89e5cdffe4285edd29e842e87e752668645009949146937dbb0f55cc55
- transaction
- c6e6389f889822d940869b1d0dd60565199eff4c0ac2cf3321183bc4fc8c3e29computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53303
the chainentry 53303
- sealed to the entry before
- 4d792c8a9e247d8e585c0c0014274131f6798734695cbf8786a7e515df4f15e0
- this leaf
- 9c827225f1b7cc9f3cc9eca8231d2829e56cb52c8b7d7f963f7bb878eb0606db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UFppq7ZBd61dmLTwARWukph9sNImI4V0U/kSH1EmXtfRmOAwr1ujw04Ml2YSE4baXp/3Nclvnqun2Ukmk4NcCA==