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
- 2beb2b6f6f45984d4f433531adf991131bea02b77b24c2a5654af0786440f774
- request
- 201eee117e7d0fce4761d483dbbe2115dda234ada900710555016d06c3983946
- transaction
- 98d8c41d6c699828f290c5aba8cc5a9acc61bb067af9ad75e848f2180a197ef6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68085
the chainentry 68085
- sealed to the entry before
- abb56ea74aed15cd7c45acfaf6ff5c780fd1fc355c7a4a4c635feebebcd166cb
- this leaf
- b278a06086d86e28752c0c8cd9c3a3e43916b5bc61d1e7d228dcb2e7a7a65330
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1esL4fC3/oLoEdpO45Et90XSDqyj7yl/3lmFb38nwRHV5wHrBns+4+8rWPlXPZ/vVI654Q2gVnasewJMdVlJAw==