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
- 32da0e9259cd6bfcedd44ff3671df03d1b2bda6e0a97966d890dc5e2bd4d52bf
- request
- d62282b56e0132c21344d2fa1dec9ae490cb18271e6167877506e4a1acf5c232
- transaction
- aee5be20a146e72ea60f17a97484110deefe86a1282209a672859c5f709fde9dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73220
the chainentry 73220
- sealed to the entry before
- dec89212f70d8d8ec660442d030497b6560bd143c96f616464b177418d8b6001
- this leaf
- cc8fa96972a8aa8289ad4ad874d225cb9523b5b066dd5b03ff3f5930bf3caa1b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dt1e+MmXa7B38+1PdCjPrIvCueCmloEbOF1FHZ5vI+54PPTLoUjAGYseaLYahzfoDX0CLE/WmsuA4gi2UGuOAw==