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
- 6c9a9d0eafaa170aa147ebc42d959e1dbc7ab18e1298c4d7d499d5cc737a1b8f
- request
- d85f83cbf0226569d5a9aaec9cc9a751cb53d6c64b25df49514e96af98ffbf32
- transaction
- 5da07e88bb9e555331f6b63107be13c8236e39f63879ec1c64d301949d268bb2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14266
the chainentry 14266
- sealed to the entry before
- 46830bcebcf8a0f6789b354c2f65bf8696db97ce20cc70500d2da3d17b5f21ae
- this leaf
- 99128fdce5668020efdaeb59a57cb50bb69310ab48519d4f4a0c8ec220ec4654
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xN0sszOBo4iO4nVIxXdnoefOzu1q1ZdQ2i2MGbDRSIbUlCiUf3el2OXCngcPnzBdtp2279lTUVMrqWbaciFSBw==