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
- c363abffc6729853b2d92821510bf8d01b3095451e93a980ddf285a781b6813d
- request
- 15c04cbe73461525e194cba9326a320a4b12eb0924189f2e24a7a7fb901e4952
- transaction
- 82a2ccbd57b49f2e3228b3cb9c39b70c2fad46cf5f006b3949f3cf8ec639244fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50083
the chainentry 50083
- sealed to the entry before
- ab56466bc83743ba4076db484d07ac93b64aa9fab0fe9094bdc6c72c551f4d81
- this leaf
- ce2d2ad8384fd0a50c5f69644319d002957f224beeeed186a031747d7adb90cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pE8eNEXz4tV/K9a3KRmEVGvek2TJzPg7RAkFSyXneW+QytdtE2id0soztgHY69jV6CV76c22R059zlqblNsXBA==