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
- f736cd7652b114c2b0b0a04195a8ec277930918c3a7748a5f6feab20afddb7f2
- request
- 621c6711161bef6af54bc29431a815cbc87eef82e00c4275be58413b22381dbb
- transaction
- c787fa7715218e1095de6cf1090e86a280d0deefec357d81d8ed0a5da2a9e51bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57573
the chainentry 57573
- sealed to the entry before
- ad3396d6daa1de6d52a37e4294a9f1e28944191469902b686f175c47654e4d7c
- this leaf
- f39e4ad39fafc2e35c37bf92aad64565dc2e9e98a5a31d9decfb789d43fc382a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2p7Ld0YmNGrsrARcNa8GgenBrqP5zooyGzrlP+DR9NSCHV+24Ce0xDqLbynTaikgUHZhCYf3mucsImb3ccxpAQ==