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
- 7cbbfc0324ba3f757cec554e2b91e620195d74872c5ec00e70e2b583c08f47b5
- request
- 4f17d3badc989318c000e6866eb4019bd2acc3e44c45a55ec36c4cfec2ee56c8
- transaction
- be6e4685bbc9d294177e7e9deeb4ef430e7bc5cb05320d12552c634fbfc65c4ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39346
the chainentry 39346
- sealed to the entry before
- b1d8072f56b9fb2aaebd09096fabd33553504bb8272fb1d659b93808b69f79dc
- this leaf
- 847734359203421287bc772a4063e97df8ac83066829018b67367d06453d5597
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 66cET1aL7u7KbzlJe7AQ038DzliOdcK+ClyGVC0TU2fSw9Bm2A850aKvOniIuM1NKcSlOd2/KMVMFMTL+OsXBA==