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
- 6527f89f86f506cb2c8c5cd0219dd9d658e9435a57429dd6def81499d313f187
- request
- 39edd80b56669ed5f7c0fffc8977cf455e441d63c7dcc362df43a0771c3f10a5
- transaction
- ab19dde3147100ffe35f81b2ce2b703a994fae30437290d8264bbbc341101dfdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54113
the chainentry 54113
- sealed to the entry before
- 7194243e530088d057682ec08704391bbdd4ea6c272159125883348c882a91cf
- this leaf
- ed754626914f9ee18c87366d2f9f75af5b4222b61568c6542bb1fd9df7ebfd09
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xtKtFIr75BMhA++kG9pLevfJipdA3YK1thcwOCCgiihsK2teAwsr8Ex16AnGsxuXoZE1MWTPHyAM1/LgWGNKBQ==