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
- cdfdf0bdabbcbc1e9c21e6b8cba77a22bb50257e5673168e5508303aaa13cac3
- request
- 3a7fd4e3f3056cf408254e3a364980222bf59f9394f964ff8b4389b99fc58f8b
- transaction
- b901ed09c4a05f1b85229888fb98820f83e09a948cf72eb74c7ae8cbca2eb47ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34562
the chainentry 34562
- sealed to the entry before
- 6d4a7fed0083da127778475a522903e49f45aa8b2a6aa25b5dab37d6e53907b4
- this leaf
- 002e36c7f26a6646c4e416615d6a124b02d3cd99f29949f77edf57a0682d1cb6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U5OTENh3YBumC8gEZHV89Do8mxT+qn/MKnRPzFYO2+c3qSjdUZI0eyJ9veonas52/6sUautQXVjyJhNwumhiAQ==