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
- 631efa74a29645554ab3cfddb3d55adda563f74b3a3859d30d6cbc3d7b21bfda
- request
- 527c6ea1f4172708bd5bd853b101aa0f64eca33810bf15211bddd24e395ccf78
- transaction
- c3e23f4007ffd43262a08ecda2160afe14ad66eac243c7cdd88952c581667e68computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2470
the chainentry 2470
- sealed to the entry before
- 5729383eb2964580e996ee6f89e838016b25943d2cce2242171d94fbffbebe7e
- this leaf
- 3bee8320cbcdc6f1c466c875193c9cf4369a5412093ac59edb7d87db5996a4a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nnmzxa14PIwQVvr9HzKHe1BNomPGkrQMRd9g3/LrWIPu6iIMM5pBmeY94F09WOjL5331ZsXz26tn05lWNcXnAg==