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
- 912f4f0af0cae43fd1cd00e4032c0aab5205385b678d554914e2fcf30666efb8
- request
- b0f743fe69089a1b70de488b3013c4bdd1679fb3185a0bfc4ad20e53a421caa8
- transaction
- ebe1c7aaf4e3ad465ac74b0b0ccef82faa94d045022702f80518dbc1f4c5aa67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14956
the chainentry 14956
- sealed to the entry before
- efc52a595473dfe35aca34eacd6932d1bbfcb303bfe0a974bea34880d0afb4c8
- this leaf
- c2c2242dc0a6bd2503fee959f78a64b18bad9bab2a57084be3dea13ef51e2608
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GsZX1uh7560PDGjy31tkb2XECNw54E7mS2OJ4JtoSPk+P4ghZ5tFuZj4Xqq06RPKVEZ/iruRW148pALRxVMMBA==