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
- 7a853cd319b2f687414ecd67377f764bc10b619346fe63404237ec2db751b2c9
- request
- 17e2f11c9fdc6ab3628be9d60c602598ddde090e6aa9474538a948560d8056ba
- transaction
- b7d879f7d138be213d3367d2fc6bdb0edb196a02c9d93ccec1d4d885399ec42acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31734
the chainentry 31734
- sealed to the entry before
- 7a18508ea7d90d78ce3b78e23f0278471abf0b37a96ad5755ba203976f8d4588
- this leaf
- 7852f14e95b135eb510fa5172a0b4ece939041738608370b469c88db29562db6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Zq5uaFbETRS0gpBfwNhQ1qNbtNkdlNEHsc/W0AL41xQaxKaMss5KODB38qe7LrCClxkjXDwbKyH2BxxeoV7JDQ==