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
- 99780537244ae64ed73c859a45542f6f502e87f1b1e88665a91e197aade90d85
- request
- 810de2af1afb6380610ce3204a020585a0a13b531c9728dfcce09cb03e555a1e
- transaction
- 87215dca7a2ca00058552744378c3a7d42e7ca49224be347fd402bcaef8e9c4dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53005
the chainentry 53005
- sealed to the entry before
- efff029ef8999c1e7bd7ddc7fea7a064ada7fb71401d8eb61f5dca51a3b045a6
- this leaf
- cff1ab9519ea758239d6e477a558db4f949e77e48d45ffa7d3c85fe1d0e39d41
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XZ/o0ly0CXkDKDNPppkU78G1n/ZfK5ceKdpx+LF13klBW0xXFmGAAAV9FuXK7xOAF2QNXpHXmXvBfuk16Jv0Dw==