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
- b6bf0c4c11151101c74f3cd7e9ad024fa46a24a82694e26c3a8ded5fe0af5d83
- request
- 54ff26b90404d8730196ef19f492c0bea42700c844a7432ceac8edfcccd08ea1
- transaction
- d9aef9377cb94d95f29f7fdb31a6b9053e209e8b545224580e3865d5995109cdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 461
the chainentry 461
- sealed to the entry before
- 8d3f06581238231ebe3c1d394deb8a7c23192858fa9ab7f72e7f0b79c972e8b9
- this leaf
- 971bf77ecc679ebff4d98f2b501c1f83562ce577c51037fc48724c40ddd36ca9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fqlQg5nWPBe8RMt2zP8SKH4vPP1g50QAPsHodvbLm6Tr1PHjyl+bZ1chqLmPyyyCCo54sv7dJCL9tYwP/trRDg==