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
- b0b173aac147c0d03eca694fcb00c6c856eeceb9d69358eaa75ce8153662f872
- request
- e5b14f2b459f923e99c571728837fea4bba24b657dc713032f79ce9e880d9b6b
- transaction
- d4ed0edf6b6e1c04474a824bb4e9c659a5797629ba6d7fcaf9ccdaebaf1c5f2dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 886
the chainentry 886
- sealed to the entry before
- 1444be94fecd50af0aa79a65e94eafdefa2a9c4902c4f30c8959f6b376164a87
- this leaf
- a35a83913e1c392cc9449d719b1320dbba843c93fd2227f34149283f16dc4941
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- scCL051UsbkUoCNzyNv6emZCfUnIY+NJrwbvkzrLN7HY7b2dO4xqJZQ4ux0bSpTSYSudcmKkEK5aTtN4UMa9BA==