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
- 0d061157ba731554661e1769c56e245d3a2c94103d29d4551bf6eb02b791560b
- request
- 503aabaf2c15d10d3946755ee9edb380d8f010ee5657609f486df5d39d0f44db
- transaction
- 9fba00098b04fbcfef7b231f08aea31947cae89016d1d1d281eabb6204a52578computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51805
the chainentry 51805
- sealed to the entry before
- 4ef8a84641b313d18568c7c4458ebda196d72f63e7e563d886ef0429e5dbb571
- this leaf
- 40707e9f57c2545d1c6f664efe8a2d8c41624a64b3f2226c4dd3a782f2a60218
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tWgaA/wtZ6Q5JHTA8tJZq8Aaw0TcPx/CVt0cRXzLeGuX9PPrs/Sq9fpq0JDijed5y8J7scSQv0QTXPJqhhCdAA==