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
- 256d6c8f019cb67d40efb6ca428b2d2a4a542fa71183ad25c59d67474de63874
- request
- 940955c9cf8268e6ce5819616de1f2539965e5ff66155e776201535ee2d3d640
- transaction
- 6f4b2a401e45536a25410d8f78bf9539e996bf7be7defdfbd861a6d7ada2dd27computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 701
the chainentry 701
- sealed to the entry before
- 4bd5e7599177ead45163c68a6b5ae0259b2eb537fa85436e087a1378e9366930
- this leaf
- 2ca6e59e387f3c3246e6c3e87ba4f16b69b6951d07594677189791423e2de6fe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xoHJqsL0xIi8CzU9CjXi/jeezdofn0YLm/NvcJrywXDzusLl6OGj7mixLbYONLyS7WFs6VKY6g11bIXfx8DGDg==