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
- d1b7ee49aab433368572f6b4a042eaec6ba40f37f2492f5e8e87f0ef2ad691d8
- request
- 878b7fe622e2a1ba407852cb1359aacfdd9ee92827729f1b4ca17ea4454b0a4c
- transaction
- c5f6c4fb1128f1d07fbf84b378c26eb9c5d71701c98d0b686dd56482339ff8bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44559
the chainentry 44559
- sealed to the entry before
- 51a7f8f43b5c18637ac9407326150f7ab35cb600ed6f2d6c627f63cc7fe6c82a
- this leaf
- 8535fd38b0c4de3d719a51596636316a33669f0700c031f3c0d9fd82d1559705
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tt4CmImlW1DC0U1B6Zn/8GgaLaS2jfjdQljXx8DMnTCw6MEdSFY6BcHYvcdJlOsbgV36odwgavBBJFHn7SL+Cg==