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
- 3e7f2c92daf15cdb010ead7cc10bef47ffaa1c4b107c22cb279cf55aa9800ce4
- request
- d78270e40317e4f0ca9d38207133d464dfff77fbdc20779082ef4adf188b6d92
- transaction
- 5491710f9c72dceb494554594c46ed0307931525c56e7694f86655bcb9c13903computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21521
the chainentry 21521
- sealed to the entry before
- ea033b694c79aea7ab0820b9f1a71a136ac34247fc3d19c8c495502b98a02c9a
- this leaf
- 17fea755071a5bc16ffd1180bb5641cf01d7f70f5292759b46a033f8e64d5de3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b67FWrvrgL6UK44CAowIU6L0srim+BDCHsY+4iucem2acG5T/I2iUCF5DtJFu5oCbWe4pJJN0OBibKtLVzIbAg==