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
- d24c068443cf96d414c535eec8dae01b80e09497edc85c14e2612fc67ab0ed62
- request
- 0c6faddf98afd87c88007b27117ccb62e77ca25339ea25d3dd8ab999a671ba7e
- transaction
- cc2c6792317c0a250ea154bb16f5ef88172846a8ab6131cca06d1ebbe9d25613computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1520
the chainentry 1520
- sealed to the entry before
- b54575d33d2787e014cd6ff296fcc2ea0a9b58e472ede44cf71559e72d86932e
- this leaf
- 047c84ee37dc14dc36c002a309d3b10f3bfb98390913a374a7a1d9418df45a85
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FNQSZLaOlg4xf/1apXRxvvJ/FkERZwrITMj+KT0DxCYfdFNLfgQFMzdAJKueOSvVUeAsszr8cKVJ43NSjS9oDQ==