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
- 0c1d719455cecbdce862754fb6d9311ccd93b16bdbd7d85f3e65a5ef45a24e65
- request
- 956b4dae9df5ce83ae135004f51aed6dc4fb211a3b6be0660670590cbf37efad
- transaction
- 581fc6148a908ccbd15bf5775d3939bc9f9c877158c2b122c6ed4c7091b03c79computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70595
the chainentry 70595
- sealed to the entry before
- 6131e1bf849713594f7cf46b3c80a9c9d7968fa3939902febb2e8ba73fbe5ab9
- this leaf
- 2e1c152d42c95b6f805d5b0f35ef28249a7aefd16c3a9f5d318257baaf515c29
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5LE4Gv7zjwPA/DLql+DyNZ5vT0sxl82cRMgU4q9xgAaJknRFcfFRMDFXti+7zfc/aYWV2zdhnCxz2eo+WPsSCA==