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
- 8da36add2c7dd2376ddc317b383220819596bbe89f1303811219cb3bb67b9492
- request
- 34a12f5deaf0652d13af2b8748fd7d1dcb76b66c956763ef1934681754d45d59
- transaction
- 809d2f01b8d7b6b5efd4177dfe20da1a32bed54c7edd2789ac6d9dad4be1bcefcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22645
the chainentry 22645
- sealed to the entry before
- 20ac3f992b865efff3bd99e0c7a312bfbf4590a6dc431cab76f767e9e4356cd7
- this leaf
- 7b41fb88f5d101aa795ce891959141c14f91dcd0acf9781ceb313380b6398c2a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SDqJ97ruqo8OZH/pNn6eqQuQ/I3Jhu/zj47LExAgkSgJ5dvj/3AyZZJn4L0v4C5tbAihQJwGInwZCi5R0tggCg==