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
- e200b27db5867f6a879aae45ea91169441db1b21b4016c190004ffd7d2a2def3
- request
- fbd94f88b8c91e50c6239a268fb103254d44a4ee00fc8dee155794cd5b3c4d3c
- transaction
- a40d676a5ba3d4125ad5217183b1cd9fdd0806332c9819bb54a6fa33887e9e8ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50941
the chainentry 50941
- sealed to the entry before
- cbfdb3e211cb4cc5a0474266fbb56fb44ff9bb6c1f7e4f54f71ae6a9d36fc6ca
- this leaf
- 00fa4b02a56b446db8aefbb09630dd67d867aecd6aec97cd6d1c99c2f9eab00e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PURcoiPgMTgAvnRPw7Zn6HwiNNUs7AIlLAU7dE14btZcVvX3FlrUrDSvrFhNFgiDYB5pnNSFb2a4336BVxWDCQ==