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
- 003a06110586f529930b380e86d4bb98ac882836e4d7788a48ada76ba6d6fc77
- request
- 591669386c5e4d9d6f91bf620e5184fbfba8626e61a8db13d2a888aeac6784a4
- transaction
- f089e5d4ae9a916ba6cc7794e5eee447ec06fe65dc0fc70a12ca68d552158965computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63319
the chainentry 63319
- sealed to the entry before
- 6af599d836a15e062866b70661e81fcec7b3ebdc2c012222e86a6a8e3c7c7ade
- this leaf
- c9dc899f3298ce276fdb258030b499dde3866862c24dd59f874470e292aeb20d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ncxBthX8B8oLEBwyO7cfKkWWrD2m176pnGccPXPZI1Q31Zqzd6YkN3gHZ9IBNiZeYCsAq+65Auuw9Vtr3qxOBw==