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
- 4dac40d5c11e9cca1a0e889fe34ed157b62dd925db583b71aa29e5279079a202
- request
- 12a28bc7e9a11281d241f8280e7d7bbd08d41fc138a674056d711d7bb49c78f9
- transaction
- 2efd8411de4024e8214e19894d9ff580a600249b2a8e4c2df57f77a55d9d3307computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46185
the chainentry 46185
- sealed to the entry before
- dd536c57c62c15f68cd55400211133f7fc589be6858d53958b9f0f25c585fc8a
- this leaf
- 6296f65d736cf723d34d2a0969dd2e491aeab886e6c844305f346e8d4c210328
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 76k4J7cb48gjcis18NZ4rS7h1V6WKxPkqeIj2AxpqlgCY+qCm+SFfA0B29BEfFnxAQCPMTPTYqvqFHigTlYQCQ==