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
- c9b3e9f007260873c5a7682b2ae9ef6f8a396d5c20e59035ca45b54eda650288
- request
- b93fa0fd01a4f1f73ad7240afd5fd4fa59a1d0b08817fd1af8a2075f6f19af20
- transaction
- ffe1ca2c85649037a9acf6031fbed71c6b0ec3b4ddf1c70e84d3dc5cb5cdb63acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58902
the chainentry 58902
- sealed to the entry before
- fb8675555dbfe7d5acabfb4affb98863fc1d1058632ce5a47de6cd6e797fe79d
- this leaf
- 63114e311fc8026009b75779c3538085f7f7a3130e549e264b8c9588aade59ed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2QKHEh0SnOR2FubKJUW2hojIrcZFU30EI5ttPHEovbpkezyjhEFjjn/vLpjceD+cDSCbMbbn+5OhgtSTChTGCg==