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
- 70ea63a259b6c5bee8801b406e41278e0601f4b957bbc9a965360eb17bec5aad
- request
- f307bc4527fcacf68ebca1dbd266c2179f282342eceadf60dc2a972f2e7b106e
- transaction
- 95f7af987612a3ae5d0c641500440937bae0cdf124ec4a843fb34bc746b764cccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58157
the chainentry 58157
- sealed to the entry before
- 7474c7d5536ea69e4a54d2742ad1fd4aacb2104d35b357ef0db3e2188a6d1448
- this leaf
- 13dd0348223f7bc3252de61219e49dba6a7d243a7f670031c2257d7d1d413a63
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YJU/+Y/pSPp0g7JqoPk5O1+ZYpOM6KZsmTEzMF2+jczvU3BeP5AMGsSuVAE7lYGE+bhpSa17K02ge+diI/dGDw==