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
- 840fe66b848eb069c11347724f851ffda18d69f1a08e74fdcbfdc4060974a1af
- request
- 70dbd7bfd6c209a2ce84d8f0864369ac23ccd7319f41dbf64ba3b2653145425f
- transaction
- 1d5b09d7769ecbb0196c1344ec8c5b6a28238231f7e91a120447820c45592712computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 711
the chainentry 711
- sealed to the entry before
- b49e5fdfe1e2718b0fe0e099d0151a83d3af9697ccce5d67ac788d17d2c0c034
- this leaf
- 3b2331d503926579b7dc689560f421ecaa9bf870cbca76d135c629a155d786ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nfLigI5qZgwFhi8NctFrZXZlQLscROSzS07Zn7NU7oHOkLFuMzJuH4ooPDbLc3Y5Grev05sfv1WG0kmyBS1qCA==