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
- e6ca60db8ba3a344886a54d39eb7ac2980fe0a684dce06b656fcf02e908f6779
- request
- a95edf26629c3ffa902076473564218d9c422f7f17142adf78207c55db9d7641
- transaction
- 7bd63c5a4886b9c12306c2e9b928b742bab71b1aa106f3e3315e40b7d5aeada8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77762
the chainentry 77762
- sealed to the entry before
- 1b06b4fb4feca3293a7266086803e960f830b03426990bd18a0896e6bddeeeb8
- this leaf
- d639a99b63ea80bacbed22eb24d2899f8db211c22fe1f5ef96176a4b96b8faa0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZsC/mzz5unZIvQT6UmCL5rssBVjzFI+RFFWW+ae9brQYuimPEN2a0BjGURAzF/UWvOy53Y+C68NZytwlRtOZDg==