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
- 520d3f6267298e0e531f10d6184643edda13421206a4b95c796dbac506963547
- request
- 8909c0c9f1f5b73b03226734971bc1b7ed80070b6274c8d7f905a0ab703ee0f4
- transaction
- 8634045eddcef9cf91f10c496fae85fbd469be0823ec4c759169115ec834e94ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2655
the chainentry 2655
- sealed to the entry before
- ae544051e2291d6cdec4c8435373d7c936e83fe81cb649ddc37666b8b7336c4e
- this leaf
- 36182d6c8e82285ad24c1953fab01b24e03a8d5b6ab3af9b71620bb82cb2c375
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YPt3qLgdy65MnjvZ0B4+512Ji90AjAgDcNmK9WPSHrLkV0yhwNEPACcZt2IEqZd8bJC2kMim1KUDl+AeWTI8Ag==