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
- 63a8972eba7cbd57faf05422b760b50f463796d4ab4d4ce835f125d57c31728a
- request
- 6ed6d76f4995a7ec1301dc3869cdeafafa59549e4f95d49dac57ec6ef4b845cf
- transaction
- a9c02e7f691069925d331b36f5d82e6bc7be1e8fa0ff523bc2d31080b3f1c573computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55440
the chainentry 55440
- sealed to the entry before
- d4bdf52d4403e4484a85968da9e6a2f8b074735efc2950f15514b8a34843a08c
- this leaf
- c0de42a92ec2f9552ca496994a0b918c6ced7c396c807f88b0e18b65b2b02558
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 15Cx3JIYVVI73QMaemxqeGf8wMkhKVIDxqY+K3zjiTliWqdE53aKpRey8UMj6JMILa+FnjRcmkXWcVqCWDUnBA==