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
- 8ea7fef43c9d5470ddcc3c7c8ff60fc750b77cea89a1294768c2babdf03f2189
- request
- a8fec9ca2b231a2bfcef859743ab6dd19440b94d476779ef17c142450c988786
- transaction
- 17062d3faa59964c9355b8cf66704f4e9799d04a7614ae5223fe2b9fd9a841bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42673
the chainentry 42673
- sealed to the entry before
- de54d31476fac958529bc028a3d1f51c6f959e8ba6a909bb92734677c007039a
- this leaf
- b2f3fc08ccb275648b99a34108445d5afd5be7c689c9cfac98b54ec76746e284
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +8IYKK1ldzBkzYY1a4PPkX7CwkS1IP3EtacRjTopXYw0j1FSZUIAppHM0k+IFWoKzxg4Yt/aYhlalB0UiJ+YAA==