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
- f5a80006230a790165f5ed8e7d31adeb0355e4376b4c039341855621e797e8e5
- request
- 46e636aa37b42ef9161c35df58d66f1ba7335b7312aa6a06a2b0a15504454a13
- transaction
- fcae7bf24f22b45bf320df751705f4d4c0b2f34b810522d7c56677f8f72acebacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21054
the chainentry 21054
- sealed to the entry before
- e7a4d07efb54a1004ba8d3573eeb3e2983f2c11539009483d811f8ce19ddaf71
- this leaf
- 85c55e8b245555c71fee51afcf5373455d4eccfa3cdc767c00a8ef743cf35c8a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BzoocKbjkIJLcnV7ZsVUFBfjlK78ekYQs5QCNNhlA8dJJ2j/5upRpAxx5e/vlB7EE/8RmwYtQR5mvKsw+bp2DQ==