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
- 6730a49cfd1a151fd8e97c42b511199631db860400f5ddf1536b1c6105237f73
- request
- c7ef017effd5a290ff6b8a09760bffcbc700b864920ed9995468ee2ec349c61a
- transaction
- 4009c5a45aa407c211a2dd92120d62795303b45bc82f46a1666037120c097a21computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68080
the chainentry 68080
- sealed to the entry before
- 33472551c459d7f58561b5b34cf81118ae829caca5cfec70388d972465b36ebf
- this leaf
- 94ee1dc2a0b85079dd04037079b3396e7d32907db3b00c33aa0dd69023539c69
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /JWFV3Q6cyR0llqcdSZO/RDJ53khJ34Ql2FPS3DzLzHa5IEAsUncoT/is190/Ma5UruqKwsdhxBS1HXiGjxnAg==