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
- c5d794b8406288aa8b31572d383d6507f262dd1312f2ef32530bd9314af2943f
- request
- 4506b14532e3cbf76a7d2f2b4fe556b38687e7df050d1b14cd1058f2689a71e4
- transaction
- 5b21acabfa18c5271f77c432c9ad99bb8909198fe930333315c802a844f5550dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30726
the chainentry 30726
- sealed to the entry before
- a07810038fb0f7d28c329c6c22b34959293d6726499f609817ff9cba47d86135
- this leaf
- b0806370cb673a16a96f8c799a76677fbbe3708aa562abbc0edcc134354c31ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 93vSVzCoP/us6hS806cGgCoP9m6eMYidKFs9hHPd8fqp5ioCIALgk3EfEA700EMuuxqgv4hvpAYM/ChnbVexDw==