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
- ea47e4b86e30110ca73fa8be2e97861dd615ba91fccb3496009ed0429ad23971
- request
- 73e4c9117aece0b35c7da86913cb49cf8b571802999d088444b30f699663203b
- transaction
- e04cfbe2d3676e9e7874a24e66c0c2222f1b19fd2b78413e0cc781f3b73e9d99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54584
the chainentry 54584
- sealed to the entry before
- c277cf1982112f80a593d825f25389f313f97eb94cdb4ceed2e2dac9a4a93ed5
- this leaf
- f35c03feebef7bc61bd1ed5a543bd066a5b8613620b7ac21306ca5ef30dd8b53
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kZRew6D3AVuU3rJRWau291udp2KRzme31TsVJgGr7+h90fFjJ5Awup7S/gj+lK1cXb/Ial2LlKkE8QGz/CVkBw==