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
- 6274d1deccdff8abc9bef04f49c1970159e54e4033e2ba4e2549d75ad1478848
- request
- 20c6647596f910adca54edff12849cbdd67e187634073a5d1121626ef853c367
- transaction
- eaee4bc761030bfb6726e57d8238e050d2a0e1003daafad2105b2dc86f458d89computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12502
the chainentry 12502
- sealed to the entry before
- 6b99ca9e8d8914ed8eaba86a025934271b2f86b0559f8a7836272b9df7d92477
- this leaf
- f36178cd5d417ccd844b9940067f3126367e50502534db3f370510a24d262934
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lp5L1HB+cbCc3ZQB/zpkySQ3EwEUatDIEceMwdF0wUg5KJwtUbrCVbqQ0rMgmTNWPM+lwHIloho79cFVYRjsBQ==