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
- d971c3192c3af4b0e5c05fd46734dc44a0701c61eb4254f62ea6a2bb06f0e98c
- request
- ab3fe423036015067892f9f07223faa209f98ff51acb74ddc89a51856a9faf71
- transaction
- af9f257d850ec2adec9f4cb8753e4930b2923d35026add8c7e695c062b702b90computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72869
the chainentry 72869
- sealed to the entry before
- f58901feb6038cccaf3b14033e423f8cd4d21bd9727dca87ec8ca0d64a8a927f
- this leaf
- 4a579291ecf3fa4abe4e764de01c208487a99f4fa49b6b50d0a2064d93da2df9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Hlq6UI3VkYiIzj1VGzv0Zaox9Y7D5R2Vi10FHLYuf8esrITRN0Rk3nxHQrJXQpyM+GzxkKQd6lFChomZ/AzqCg==