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
- 2576b3e1db6e974122d7ea2f2d0b9f1be9de5f3b24772a27e410febd0678026b
- request
- d1aea5ebd23e09f4596920f547db70304e3ad2e56385fa7202e3234eb93d4b88
- transaction
- 7fdde36eed6cc2955aafd71c5f7a01ff18a9c3263a7d64424b90c062c7f5aa33computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25098
the chainentry 25098
- sealed to the entry before
- 9ee633c9d78d4c9fc30265191e596d645e24bc524bbb94e450a9a7a9f1b056f8
- this leaf
- 5f8a87afd78cc83310d4bbdaf44d586c04c306236cf2713afac1c2b706b9e621
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sDQD6R5a0n+OTh0Nk6zF6EG5uuK+E3UpO4BTAEr88LaSmb+2rz4Crpji5NCU7jWQuK6XKl6Su5Ms7yNfXXvYDg==