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
- cc82ca49e4b627af0fe500ef469ecde2dba47cd4e84cb89614749855f9ed678e
- request
- d89ef39ca6a500cd1e88e9bcc446f55ce0749dbf3e12b0ade4fbedbb10cf9fb9
- transaction
- fa1e19b9e8f7edad32bd9a09f083fa00e4ece3ed6ca14bbe552df1cf2fbf190dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16540
the chainentry 16540
- sealed to the entry before
- b59d133f05ab55c80290b918054774fc48a6dbfdbafd790b26fd942dad4a2b80
- this leaf
- afc2db97954d43b2f377ef33e25c73cc1199ac1985889c2a94a62605cf11026a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KSuCnxpCpr811VTdT1q+9lyd17a9LkD8NvfvWRwUqVpzDzLKbvRsI2MrozJBK+Bn9nfSvX+FW+xwCIXiIK7EAw==