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
- 6599eaf72422c4795ccffda3a75c01234afd836b21621c53a73b1313b6a63765
- request
- f334779dfb1c4840f2d2d0477721f329d6287e2c38affbf9b6f72b77ae7e745f
- transaction
- 52faaf89a058bbd8841df0815db718b282b157d9b8eb48cd4ed11708b4cf8669computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29488
the chainentry 29488
- sealed to the entry before
- 5ea755bb31c6b5f6ca480f98ff86be6712b4578b2c1f1d423ceb1af91c4df02f
- this leaf
- 0daee4aa26264a9e78f3decc5c6d9a3c626e20f119fc42375092bc71961e5eb2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HglJ5Yg6Ez4k6kVi67/uFs2pC/CqsKrMYvdHW6ON6bwmXLDE4rkumCWqFpdaiw42Au613zm6CT3JU/IIKYQZAQ==