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
- 8770aee713def6e3bd0914ca7edc369757b7fe437a982308795971d38ba6fcd1
- request
- 6a4945fc4af23ee293e56e2432cddd767e1146d9b65ab604140929d16078fce8
- transaction
- bfb83829cd2a22b0376bfb68deaddbd8842d074d0d8508693bcd7eb1eb0ecf84computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21414
the chainentry 21414
- sealed to the entry before
- 28f79154a46828cd3b1f5bce73cdf13e7eaef810b967f17d15da5c03d2d1b457
- this leaf
- 69d06dac08f4f74ac646d56770e972f56e2d07200f82972f33378c8c17267e71
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wGbfBxqdXpqlpRhjUQe+Kpw5CYiPvfMz5NNdpFbOTLhm1Zje36OQCi4AFNMnA1QxFr3RDWzCNltzS5YEwXw8Dw==