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
- 065610a2bd34f0bc2942f9bfa1d9a1ed2350a1b7c2812d8daf2141818db8c4ff
- request
- ec8847b459cefe30747260922d3935119ccc68f44be9fed434f370684fcf1671
- transaction
- 168a0a4f1604dc19419d872c04ff15945a16478b3b5f0469ee14086473a72935computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31822
the chainentry 31822
- sealed to the entry before
- 6ec8611a072bf4981288159c006702ec4347847dd5e611ef41aa724757bee027
- this leaf
- 299ec188117b13b7ce093d0451150a4a5afaa082d58d3446d4304cafa434db90
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DqoM8ViBo4pOb/x+Nmcdsg6oobTzcdDKs8Dog7DRgHIbKgBuJt5Okv6xPDYuey8ypNrGnhVw9HKDSuF7hFzfAw==