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
- 96f46cde4b70a2b937ab9804d97f1e7b438d28313f25aaf80c2d360b8893f3a3
- request
- f347c7bf507852e9bfd9b363bc3bf6333fc5aa617ee70d9f07d0071205165238
- transaction
- f47fb2912b16d42a4ae76e9ababc57bef0f6619673655af5a6b1df7141e40d93computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45420
the chainentry 45420
- sealed to the entry before
- 56953dd1d9e11eb952813428c75f682cade3bf79e01d61c6d5bc316649dcf09e
- this leaf
- b15809b687ca3fc4f0706300b760517b3f5670ed2c153b7941cf85678a979433
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZPu92yOCDR5mv9bJtpUk0Vj8xn1VaYomSlSEpjjwq3mD2SdoAGIuAd7eqER55tE4CB7ma6hOaCu16JlbuoAABw==