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
- 03725d3866a49a45a1895b9c8ace3dfd5ee2fbec552ead62f33f9384f82278ea
- request
- 97a68263f270fc5553843e698b6f17b8c99feb12343f6930dc2def0b3bc1b052
- transaction
- 2bb58a2219f104f7e7e6338bb4ec8d59a22bc5024276c67a1d7293de57d33546computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15045
the chainentry 15045
- sealed to the entry before
- 71627dca39cca3fb85049bd6fff6ea0c134cd4ec9ebdcfd25c6e855f5d01ba53
- this leaf
- cfb646451fc66424aab4dca020ae2418bcccd3774bb2976f47198ad293ed96af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kA6Xa6PEQRBxOVkBqkiWjcL1rZZlhsz03ovUckhwcBUaQFh91hJViFGpoSbv7SfhP0ffNSsgo5U6/jjf1e6zCw==