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
- 4dd926ed974bb71e948010343ed44df177f0457aa16c6f56e79a102cc0240f9a
- request
- 85dc9eaed973e977c88b5733ed380ad0323245541aa9e5fd78690c861470e1b1
- transaction
- a23d82ef5b4ecced0997a01cd8524bb0c521fd13774c442a7f15ac781f83d79ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61971
the chainentry 61971
- sealed to the entry before
- ca860be32835f098c7d18bf0784657e676e92ffa08fe165a0ef280a3206ca13e
- this leaf
- 7242e1121186b38ec8520df7056527ca6eb300a129e72b48d61ece0370ee799f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JdJ8B479UjbPCwMCkLf9pIKthhkmI4v1KfdgpvVwqv+1KVhfUlfnsAWFvPqP+NSmKPBRoB48APgSzx8HMDtOCg==