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
- c18584061664c595553675698d26419daff3d33762aaa0d241c2028409ef535e
- request
- 34542baa809adc0610afccac6414def471de1adca47650a45ca65edf59cf5bd5
- transaction
- 6d9fd527f0dfe5d23bbb8ad7cbbfaf6a3cab3e3a4e082c5b4a2cd14529895571computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14075
the chainentry 14075
- sealed to the entry before
- f609ffffa7e936168902e4a0019a4700f41a6e0b3ec72d7537710f94e13e3182
- this leaf
- 9f40e77295a34047b8179a72c8aed8ba447a77170f55abea70af1dfd5923c5d1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2s1Z1bEaHEbP2wNo46kgRdTKgaZQtEf72DmYzH931NAKmt3Ji/50bVNBoldA600t766PD8XtDykuYOnEZ6p9Bg==