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
- 76057a4f4ad2e20879745296fcd186071a3ce4cc98aa41cb1f960c1880b100f0
- request
- 79327bd4ac5c4080c27451e8dd60ce6ef36cc71e37a161b506fc5d768e44eab0
- transaction
- ff5debfd64a57c138ca0de252a20b552a28f8d2814f985da09509900651b2c34computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12130
the chainentry 12130
- sealed to the entry before
- a30ed2a566d785a8c41fb0484c915405d198c54dd076455cbefbd6955b61b557
- this leaf
- 583bc266ca40016167b3b2aa558649e3cf65eb3dc338c64acd0c5b283fe6c21a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oRuwA2JbnyS3N2mYz3yNneXa3uZXO2TQKl8V4vaLvLaNmZTpDTlf6hot3Hh4efD/DTks9K0nV3lS0MTxN1J9AQ==