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
- a9366f3ea2185e7d10b2f6454c1210d0f8ae660b25993bc08dd2ad34fefc3267
- request
- c5a252827b4ce0183f7f97ee40688d0b3bf8b79cf7f31436df682b4d54c9a8c2
- transaction
- 826928c90905445d5fe690220b4f12826232909c444ccb458a0029c2066b841ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28640
the chainentry 28640
- sealed to the entry before
- 1d7969878d93a2e8c950e431bfc35803d969a8456ddc8f7eeadf04af5adde3f2
- this leaf
- 1d5fd5e56a2d87cac7e291931d1b007b945596c36cea1fcad00ee909fe51e722
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9HnDeQWErYjCt5WmjCF0DjsnJWJjeJxTvfd5Wz56ytXSeGdibOaoIoc6hxcSznmf5LXic/3a3br9qyVyyXN4Bw==