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
- 79adba7b6160f811c9c0a61f0f1773f7209b80827608bc9fd584b0db7853eef2
- request
- f4c553b4d14dc7e3f8868dd0f549212dab19dce10483092e041454d525b7d061
- transaction
- 1de91377a0342075afe74a0e2b747c66ef5fe2119a3506c53c2aff8bbb80a840computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42069
the chainentry 42069
- sealed to the entry before
- 7f6c05b1eee74eb3cecd29d7b896262053424da7473e85d1adf97df273abf6bd
- this leaf
- 45537b8fccd567886fcadd8c683580675eef62f1de7da7f10ea517f70f421826
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kma8X2P90Xg3mGWB2UO3Y4ZnAKs9hH7ksNI2MgaMap5lw46LxlTen7hcASUFyDm/k4ZOGYO6+EZZHeHHBNR3AA==