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
- 5d7d56589397daa718eae19633a9d73142ed23a15981db20140d093f3cc02949
- request
- 10795426807bc42675bc30efe6072a84d9503bf68976bb26fddcd5989d2ea39b
- transaction
- d61c069064f086134a082380c88b763f4aebdba1c3197d024dc3ff46d155a55ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6275
the chainentry 6275
- sealed to the entry before
- 2c3dde631163c27649a08a0493f02f23a998dbc54745ba1a91690511da3b70b9
- this leaf
- 0d64da4862cb34017d7b812b7338eb589e202dacecfe13a14f11ed433ac7420a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FpZaUt+Mo1ZA4oruRjNb8TpKKA0y65Y1MyvAVKXtZJvpPhScvDhc60ra/LSVmyr1aC+VRzbYhtJBOvG7APlACg==