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
- e5578eef2d130864b9f3c421d1c8bbdd0ddac89a9be27192f6c73bb9f9487dd6
- request
- 7db97cba27cbfa64d74220040a10c2d515bdb73769c3c932e55f7bd0098e940c
- transaction
- 43d1ad22eb88fe5420fbfa20a196672b50ecbcb291ac6a5060936303a6dacd7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20262
the chainentry 20262
- sealed to the entry before
- 6922d1b5b513e3096b7c39d57212d03334a6613f40eefa21ed1c2bfd8b4b58f2
- this leaf
- f0f660950bf3b0f2b8d646f666b20b0bafc868f8b99eb31216d88d699f41d382
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sBIWj/QHqCcc1lLMIfJg5h7zRJL12ZEXY3qDYoK36Zq3N7ojBTcNuruTMq3qrfGdJzTe8mqKndrsDZPzTHQqDQ==