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
- db05e04d30fa5e0c4dee05af9411f8af7642043be98ad71aab3c97a891732e06
- request
- 43edd8c348721d40d7c3ecdd5e2aee6a3d949621636bd4293eeb234a68dd4410
- transaction
- 261fcc4cf05f5070fe8eb915f3f84bbf6f093c994c2b7ed319e65f9524496014computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19778
the chainentry 19778
- sealed to the entry before
- 31e376f10a063a1ce8559855614ceac89a568588c1fe6c59a609d258c7ec0af8
- this leaf
- b5be6a52ca20167d0b2a8648d0c8ab157a6053d15f3f4d50dc37e1bf915816db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- i/wR6uizIDNaDEYnC6BejJ7LoJt0IN+IPBOfjOAFF2KGioFe73OsWQ7BWtX4AekDGaiCqzzrnNHj942cjAppBw==