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
- ff70432361e0c207b33b9ec426802f1a8685c1429890a147fb7277741e13ce95
- request
- ddee89531b6b24820a6eec3b303122854bf5dbffb23db81168c639b382ba3736
- transaction
- 2b3e68d1c49f81591f1aafb752714a59e643439034b8e196e243eab7ef4ce7edcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2360
the chainentry 2360
- sealed to the entry before
- 66590b605955862d1252c144552aeb7de3439b8714973a80fc9206cbe527a624
- this leaf
- 3da5999c55d0e3e403957e45462344d1a119698d1f08f03e50fc9c22eea3e2f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gzPCUd+iEOdE2o4Weu/9ALE209lhBe9m5UOaSmUjfr2u8k136h6TxDFF6jY2i6aqZQ6WDguf/lcf4O6lcIdiCw==