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
- a54618663625264e73fd1355decf65867d4860459eedb4551830f90e2d9633e4
- request
- 0361ce4b0e8cbfdf76c00b292a4977e6a3fe265f627d1183ed76a997911df922
- transaction
- ce2dade263713ae30f3bc99bd51fbdaf4cbdb1a27502b9cc6af69dee88dbf6becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30280
the chainentry 30280
- sealed to the entry before
- 646cabeb934607600ce547bc3f907432d77ce643a0388838deab16847054f0b4
- this leaf
- 6e34c1c51b64b38862e85d456cf107bc4200c3b7aa7c280f46b994bacece0513
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wsNjdwSxRE72KOwctNkFpMFRVxXW8aMi0GFvZmNgmDh2RFMX/2Z/xc8ZDVCV9co7XYj0Q7JXTi8yQ/m7lIXlDA==