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
- b793d4a2997c2a49dd80c0bf6479d2a29715ae73bc52d70393a3f2c69eabf732
- request
- bc01b602c72c9bed0b2d0f912952fbc40f28294dcde7c61a2be5654d6a0f17a2
- transaction
- cfe219ea8c874550918a636f516a7edb00e8fe3972aa807dbf9496f54c00de3ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53323
the chainentry 53323
- sealed to the entry before
- 0e40a062f40873bfd56255fefc47ffa50e4f694d7a354410c087a18fba4bd008
- this leaf
- 07addc09d43de50ca94154f5b230babb47664260b2cad8f71d51c82fc8a6e7ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Eh7iD1kZ7lGNsO1TkrVAxtPtsDN/6JiXiLcendkEa2ecFdS/20YzgPKCJaFzLeXTzhY0OC38k1reIaiZcbF9DQ==