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
- abdfa81d0226675a79dad7e4b7a83839e9c4b26fa360d54b02eda3dc538e97b7
- request
- 26e8c9a9a793affabd00cb455f2b7ab9b7cda63d1263916b112962030d0ab0ba
- transaction
- 51ce901ba5e68a23438d2fa56822b072f039b1bf786e1124c9416e1406b3fc7ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53092
the chainentry 53092
- sealed to the entry before
- 21467844d43f4eab620539425bc2e3cbc8be2632d96e56d8334b90c6adfcce30
- this leaf
- 5e62d305fbe96c272cb256a323f2b7142c5c33d9b80995f7480576c88e0de1c2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e1n5TURS3ZrBw4fObGckSTVASeXBxpNL38WNDGJKatYo/C8B3K71nINUhVFBo+TSMtPA8xndqQXsc83NmyNkAw==