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
- 59df08a83218e579c4c8b1a809733515f06b8182b5a046f76bf23af40f2dca22
- request
- c895f5ec8899a30b0012b0eb9e907aeb606034d4ed947a58a6362178fa48f50a
- transaction
- 3a5af36816d1450b9a7d3c7e5d588ad32a716c3ba1ee10c9f91eb78593ddb92dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44663
the chainentry 44663
- sealed to the entry before
- f312ad5dfcac8d11579811460f841419ce948fa02485103a72c67342d22d44cc
- this leaf
- f9ebaeb721aa6832deffb0823b7636b847a0ca9d71aef6e56c50c07b2d82526a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HdnK8R+eQjaMWDaYYPFe5+NoCFk7vqwfLqCeKsCJi8gXOhp49BLcwCzUGTVUBdyJFRyF4KjBVY69hX1qTRBaAg==