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
- 106b5a4063b60f76fdb956b01b809033c2ea9f03bad1502627aa1b07086d8284
- request
- 265d65934d3ca0350c7aadd66318515c33a78ba4239956b8c98724ac41cb02cd
- transaction
- b71926babd59905219d099fc9e34437fb7aab10adb023307149a415343d2ee20computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38323
the chainentry 38323
- sealed to the entry before
- 0ec06a7c6f4816a09aa8d3e5490e595ec43fb9588dc1c679acb2377acd4e60a1
- this leaf
- c0f4b2e649ebbb0830003e8864125e3ece6c70aad010d49b98894de5fc97883b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +F54bTn4g0cE6rAN6aVz6hPjE5AOi3IYnYzuoU3vvQo6SysKVVbqtrBp/W3jZ2tXOBAeFuw8nP6hPBreAaGuBQ==