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
- c549a9840fbfa014884f41e10045f1a8cb2f749937b5fe0bfb27635a48b7444c
- request
- a4bbd7c8fca9969c604ea3a90414cd33a7946f0e7ac6fac7239b49c507b0cc38
- transaction
- 11bc5712cc9aba5ea285d6cab9472f29fb48f3d3e652700d9e38955f83947400computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70062
the chainentry 70062
- sealed to the entry before
- 5f203ad9e524a6d7202db6aa19b07f61b37dbd05e2fd6b923ffb9d0badadd3ae
- this leaf
- 2065692cb902938d887dc29340d274e174ab8955da492d6a67ec2cd4e84969f2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gG2hFdoQvY4dJLvpsIpbEMPSKrhB7fTnkK6y6SyFjekttBBwqfjML0RCMyWicqtWWJl1BILaUJ6FCBoIIr3nCw==