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
- e68d1ce8f56ccd744ee36c7db16584ac5df44788757bf2344938a40a4892eb16
- request
- e4743d2dc53c79929a95aac4bcd0d3c23e557351b09252822546f1e96700e955
- transaction
- 0d1a2d6ed7e1983201702be348d7ebfa8ece7150e210fa25835bd885438f4de5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34862
the chainentry 34862
- sealed to the entry before
- 84430669f11beadfe66e7f207314be3efd01da32918ff5a62eac609bde5ee9ad
- this leaf
- 5ca6c40433ec8da1bf322cf134d5fe024a2c64a7406d1a7921c13581e3ba39e9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5j6p/m7seedE+9U9h+QDRs7PCLqM0s5o2g128tx1gB+da0l0xvSEuVDcQ5kuQCV7KjZu+BG3kRST+A9vqdI3BA==