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
- a635cf8d9f41f62f771f1ac488d4a5ddf317773fe86548bf33bd97201c7b5279
- request
- 94b4d5496a0794788d9d3e5ddfb4a85943729a70046fbd78905ada4dd200d258
- transaction
- 35cfcb73f2421ccac3348b0cf0dfeea52e08bcba80556b772a579151b15654a8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48931
the chainentry 48931
- sealed to the entry before
- 4a5fa0bc4454d6470ea29f23230fc57a810f913ea8a168a47832a6bd7ed738f9
- this leaf
- 1af18369772ca7caf9c99ab27979382300b748f09b7a8ab26f0dc167495da4c8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N7azKuAk3cGicuHoXDMxanaFgsaohsnTfPnFAALXi4cY5avShiKICKRAxM6X/RIgltGgUkT2aeXu30CkmZZQCw==