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
- 5f8417eb95c2152634cd04275f2534b43d3eba460699712d9e20f629a63de68c
- request
- 1514829e5175c56129795c2afbfdc48cd3f7034f4879d6c126177b52d10c5631
- transaction
- 984556254b930415fa8b41840bb83b2e72b757c448dbc06361f377d7937c6272computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29023
the chainentry 29023
- sealed to the entry before
- 91f51ac15860beb242f3cfe261099a417a084b947e066165f48744b13440af99
- this leaf
- 248646dd7c05136a257313ab72e7a3aa6e86ff08dcc8af9c70f49e2ccb87080b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- B8pzqvnYB0eNd3yacXUwaWx8xzyn79iceVG9vreqYChrCZeLj6Is9BLORBS9430G/WWBlY8FIFCXLBY3PGNPBQ==