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
- 8e901611c8af15323a63ea7ec8ce85c0ac80b1afc8a584737944d938ba7f646b
- request
- 0df2b4aa48a8d2c12dbe10f1a13f618dd9abdbe74e8614747dd675a1a773dd92
- transaction
- d1679b1baaa3f5138e104a5e05a48b3550497b9cac0d8bbe0e6f23233cf1b5b9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42198
the chainentry 42198
- sealed to the entry before
- 7838a2d8ba3a8af4652311c9105cf59882c60b7162d604aa8cb865166ef8fb3b
- this leaf
- ac6e25c4590db66933ddf51d070eaf4dd55b6c406419448f95921c54e85d8528
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6Q4haUwRwQZWY060ArXHFPENxQtobFHDHGCqGS2pk0eYe8XhX9OoGWbO0Zad3zZ3C64GmbCpM65ZZBKBHVl4BA==