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
- 236936655f9721692283b343062271d350725590b57b944519f71dadd60cd7c6
- request
- 0c04571b744718e956d9cb8e082bfb3c305e39e13542027420c33dafb039bc93
- transaction
- 3bdadf65211274fca040d5b490f6fc6cbf72691cf2f5b33b68d98bea7b7d0774computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40467
the chainentry 40467
- sealed to the entry before
- 523fa3ddd8277e87eeccbf546743b6b60ee5223fa5951a228ae2936d4aee8ee0
- this leaf
- de360ccc9df89dec1e4ff001f9f0a768d6bfbae137368101504b65125bc8b002
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7UXC75t86lW8pHbxcb+U87U72jL9BeVxVmA59LE8L3uh+eYXj0haZj6xhhHhK5Ds+Xmzw9/wHWXh9CehJbSfBA==