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
- 42f42c12bbcba6498aa3f32ed8358182689e79d1a528942ac8ca14000f0f0beb
- request
- ba6e6d133df6513eaeba210079a0b6afee843866c5fd0e2b9dc0379a055fa9ae
- transaction
- d44ead901fb4b139d8dc950308ab6b56045e13abf04e217885715a2288f478a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62830
the chainentry 62830
- sealed to the entry before
- 9da4bd7b77d48879c883a9f690b5fd0326ceb80960a99cb73b64554db0b8600f
- this leaf
- 39e795bc60bd4fd5908cb7819a9ee95874a2dbdb19c224d2d5bac75c129f52d4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NNsSeGuzLJeeZLCrTEruPt/g7pPsRUz2ZlmUUu+J7dP07R5KafeG8aS19VktpZXm8ZGuytQwTJ6XKMMmCGYTBQ==