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
- f3ebdb587f453b414d7e876b3ceff3beedd687bf5688846dd33fa20fe74f3908
- request
- b2f5adfe75a69eb26ee0c87472879fe3fb74916477c547bf769ac82a7804eda1
- transaction
- acc5fdb2e3d462d98f300e0ac1c5b15ef346fa246afc57d9416f845f6d90645fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60178
the chainentry 60178
- sealed to the entry before
- 9b8b0cbedc5aec4e3ac8ddbe147c395004c4d0c0e296a26bdcaa377067ebadec
- this leaf
- 6e60a6533c05bc2e1a6e0747c167a10bd18bdef7de25bf6bec17829ac655d199
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DKxgXPPmLeWVIyjkUASLZAuD7V6x/a83rf3bwH/wVPYyb9VocSqTEPu29HrWNCZIZ6jUxdNyQIW38z9DBudDAw==