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
- 7dacc52ef90128e3be94be29d62ee97326662d33bbeca843a613c0dff6f4c1b1
- request
- cd19cd61d31194a3ae40b56e919e9ae0a4e50832b77465ab9bfa1a4fb5611be8
- transaction
- 65b70e041c33a882197086cc176e8a6061641460537c9caf1f5570010615fc70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68177
the chainentry 68177
- sealed to the entry before
- 0b726ad6277d1b5b3846a3c9adb21facecd90db8ac26b220d268aa0f6f48a725
- this leaf
- aa130284d2b175f573013f8f3fe11bde915182a17bcabf15ccab0d88102afca3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7J7SCmdlRs8Skhca3MaQ9P1Xc6fWfkWymJAREINKSqJrFV8r4FWcXxQgRK/+o1oM7ae0pmQPxSbWZD7zLZ9UAA==