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
- 3b69e7372426eb8c86ac0942972c56c8559c95d40782b1f5982d808d817a8e76
- request
- 9265181fa6b3c6926ef561035a0563c34ba4e57d0fdeefaab249738e090210c8
- transaction
- 6d7b78267ddb016ad905423a377b3d4446f29d5ef90fec16d7786de4c02ffce7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1425
the chainentry 1425
- sealed to the entry before
- d75fdc6f2648e9949a2bbb58bb2c4caec8cefef76851be9ee3a77390e4011bc4
- this leaf
- b79906695ea9fa7edeb45ccada9d53d8c6d30be7d8a77109b8342b342e80ad8e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gka/ZVbotuhwlk2h2JPb3uLcraTB5+i7gNVcLrKCdYTtz5WHSTH55jUMQmYRwzKXk8e402apliVK1lOHLr5+AA==