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
- b0594aff02c4648ddd8c0bae84802826d5fa061a2d369ccd0641275bff4b1579
- request
- 99b141aa4d7f2afa6d6ba37d87e7a7307bf902a31f491bc36492d23c1f39c5e4
- transaction
- 2bd38a0fd1bc67222ed445d770c26fd228b5645ed3c572b9a2193858e95c0537computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40680
the chainentry 40680
- sealed to the entry before
- 24144835f6a809e166d516e4500da2b267622882e727bdd766031b1d232f3369
- this leaf
- f2e7e8d532f8e891f4a26bfceb2ae3ba33b898dc1183850ccd048e5a0a5b84c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KBntWzUVzp7xXD333dYiWwbRPBTprfpIZOYbCu7rc9dvhNcb1gaVblnJ4vk2S/MsjRv2TC1E5Oki6t+WreneBA==