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
- 99e4e615c6c80121be7807aa3a565ff314e4f63c0c673953bc33a1ec871a40f5
- request
- 599ed1868ff1b204aad1daee542f84c35af655e6ce1cde9a602b2abbcab8186b
- transaction
- 361c9c301863d8099dc194b54719205f2cae6688cc6e408a78b99b498ec91155computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9631
the chainentry 9631
- sealed to the entry before
- 17115b20cbe3c38dc65a6c200e74a1efeabac58d5e209bf3dd1b3e449558ac9f
- this leaf
- c1df57ba969982d4a49cbc33253606dea416ffba34b9ea61468356ec2df5a3f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +TTVAQ+KR1hQxTwaoKpcmdhzboFWSBOcIxLn6IP1grRSTQ0n82wvdSv0RAB+Cqq0DHNgcQkTzW347P6hjTcHBg==