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
- 58f7410711c213fc92070b82a0c7525b0cd8aa1f9aa5f0b69a9356ee02290bfe
- request
- c44460bb22bac5d8fe82666c2af4042d0232f30e5d2481e21998c17c3e8867b9
- transaction
- 77726ec2f9e9e6d1c354c2330c0329c8d80560a5d77de7ca2904997bf4e128d0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54879
the chainentry 54879
- sealed to the entry before
- eb8c63c8c06beb2d1b03141766ad2940f9c17a6486613bcee286d3d9595f669c
- this leaf
- 24d168451ca66a781e7ada45848c78bb9723dd524c1b495c1ea7e4b559f05040
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4w+dhJeMkDjGl+kPEh6WXGZoXGRB9Wvv25i/xyX/Q96CTgsOE9+lcTFlPUAYWG9bagxkk30lknNPPjHnhGdsBw==