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
- 69c57aed301bc3c5d977dfd61da79508d07bb7c9b466e6ff1974df1734efb090
- request
- a72b86ec6ecd0865c458c6be529b1e134e6392afb8eb27a2ab025d6de2dfbf3c
- transaction
- 719609e02d3b824d0332a2429432e09d8f10c4ef9533295eaafe9fb79f741c70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68499
the chainentry 68499
- sealed to the entry before
- 8f607a972487474b7359926aa8e7d4af97083659abad0785d2ea34c41b7a64f9
- this leaf
- 9a46b1be53d0ddbe631d6f5bf0768e129ff12e71f39a8c79663e41ee868f77da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BXu0VuDGRPmIr6d+tX683jVEIj7HTNZffIOZfiMw9vTTIYChl5r3aR5yZn8TKoopmiDd8zIM1XSxep6sTLcaAA==