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
- 11c39fac4255fd5618d6af33802be95c4e26a3eba13f5a2988093b996aee6de5
- request
- fa3cef3929595888ec16ce49d1979fad003783d354c418edca680df8c92d63cd
- transaction
- 4a2d556c66e3f4fe46e3b76fb40042f28efcbd9bfcadb56b408660323b0c6157computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45919
the chainentry 45919
- sealed to the entry before
- 694e70442c4c03d7dc896c696b182078e57980a9789345c2d8a2a3340ffd48fb
- this leaf
- 43451f9a9c29af655cca1022c597f1b6e804a7763dc78905a227bb47575e9a6c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ThLk/I1UZYu2ZM8MQPD3XYOz6x47l0Fv0cwWw8g5rjVsBjZjifQlxj4Alz95SIlHLXk/EYgTgF6BpzUGHzY8Dw==