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
- 15656ba286aa0a3748ea13008af0715b91dd484760cad7de027cf3c0fdfdc05a
- request
- 3117b7ca394d031765e1dd7ae4d462778711358cc9a3258e2b6a0f83b65c7768
- transaction
- c18c438d8448e36056c3b30df067dfadbad4498f5e011b75e7f94dd0deb9a979computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74522
the chainentry 74522
- sealed to the entry before
- fc25ae69be9c92692e7a213f4a4179b5638c3de39a23bb447a9ec06c7eda71b1
- this leaf
- 05870a6833df2eb09e684140302e948957ff8587bc4eb4a097ec0a831da5ddb7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YsA4vVWPvRKMWjViLtDKmdgkNUbNdoMJtnfi8FNBF1KM4IY7Vr+KKlzB+LwlT+abqTmLP3mTbDwwC/04+A/zBw==