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
- ca711c76c0d4306270a277abbb046b226a97de523ece1239b1986b5d7865df1d
- request
- 3a8367bf784cbf82e22badae7b2bbb6c44e41e223d7b36b852eec89c9e0c1630
- transaction
- a1ae2e3a1b027ea95b253d74bad2543828fbe70fa19a4271be5682c215ae45d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 676
the chainentry 676
- sealed to the entry before
- 23907b571052aef2fae376836eecf278fc46ea6caa684552ac97c462f247ba86
- this leaf
- a79db30e4a9fb5e5f0d8e9ff02c0a111ef617872c26bb96c53a2d66477becab8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 38bbgZpz3BlHEVqSn142iANUOH2uWGuLR84tdk5FG41YVif1TYUGK7cFJsNcZlTLS2TyJSpg4iuF9m4BMUisCw==