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
- 535c6f81518d7af1ca98904383031cebb3bb9a13dbb477b2830afb5d9c62e77f
- request
- 67b7176625a333ba5de59f21b5f55e1262a30f78a0cd19a979e93c50edf0984e
- transaction
- 0234ac6c21088aae3570e00b60f196112bcc2f205f9939c5b72796c9a7530a3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 326
the chainentry 326
- sealed to the entry before
- 7e326c097b6215ea609383ffe82f44fdf7eacb7d2bf7602ee5518eaee5c5076c
- this leaf
- 42987e3afb89df49a1e1b434a13203449401448b9a093eb2b460fcd1eb4ddd57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Hg30CJsxhMxO0Fa7Irc8nRwbCmhzSwJygAxR8jpa2yyteSX7oWDe/gIupokaDrK3FQ1stI00jkJ+twIrnyTHCA==