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
- 66784ca5fde653ef8b699b6390221b55155cc252b82df2359076f7c34c00225d
- request
- e992ea8ef8fc90b22d58ac6798a5b706d6c8859bad8f9db9c3f355fda8b4ed70
- transaction
- 4b24f635ee5f0485417dc9f509e8cca5f72da4e23884c90b1773c2db60767911computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5406
the chainentry 5406
- sealed to the entry before
- 66a84da96675753159b2ba7b92887b7437dbe0b826a780d0a247cd4cbfc2090b
- this leaf
- 53e405d0fc6847d6a0bfc8e0f9fe46d3520fce0615fa84e77d9fef7b767a5d4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eYczS2UXFz4lDmgQJah9ulJmdjN2U4kKBaTj2APSL+Yi54ksVNK1wQk30FiQexWQ3jpYecoNWEdPjWRndgpQCw==