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
- 59154802b73f860014120f3b78d821d2cc345b5e175923d9570a5d8d4a2af786
- request
- 1ab6eb0ad533daaa570bc77607b8147584333246ac40ab4d1ec775c6bab9b14e
- transaction
- 2b44843faba2140a89b22b9378fb13586ab48a48c2d3bc4a0989fe1d4639da30computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39888
the chainentry 39888
- sealed to the entry before
- f7276ca68f151cd5211de196bbed7edebf5d04c1ade92a68b106059ee8033448
- this leaf
- 7c69131573303f176354c939c06777728a0d59eb306957a35b1953b9830f185c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- k5hLRRi9hNKSWm3rpJWzU3qFL+RW6/6RCjCUx0xAeiU90iDrspnMVwUReY4FdzpzPEv5+1zDXpOZkCePW3dYBA==