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
- 36db5e105ed32849f05eb262786be535cf9d790f251a09795a7e5570cac12809
- request
- fd3b9baf77400c1f6af444ab3c600a3f3c617178761f94ba05be332f53d29715
- transaction
- b83c49e19beed074b342b83e2640f56e62d17d8b5083469042d2bd8cd234d68fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2335
the chainentry 2335
- sealed to the entry before
- 0f5a1b6701c50ac6aa8fd7a0aab59071ff4431a2370754ad433f62c892efacaa
- this leaf
- b10cf7ea57cccef66f03e23eb777a99710776c5ae7947b431b812cc216912aa7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UmCq+ru2T32qXpmQtIs4vvPsVlZ8WUjDmEFb8NOf8381O/N028zQOUniQQWBwVAkpmjH9h2imolqZwOmsd4ACA==