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
- 3b85a1cac7cb2f631352957aa121444cf3fca6b941aab7e98df572ed9bd7f298
- request
- b509c9a0e21bb9a28037fb01127072ccb75e61c4c8797680059247014f9d77ad
- transaction
- 3098ff629578dc0d34b77779c02da3132b1e267a600cefec0161bc94cd26bd37computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29081
the chainentry 29081
- sealed to the entry before
- dc42bfd6d34608a63b30aa24d13d2cc3f0916a860f7ea359cc8ebb19e259d089
- this leaf
- 89bba206e5a4670fa59a964f95369cf5670c6fac9f3df80d7f240af27d1e8eb2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 69NguGE61psSQJ/VQDBBwWCZhdUC37idlTx7r9N6ztflPZW2i4juD7Raxjg85Za0tB4UsS8U5raIVVdZHcMUAQ==