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
- 42a6f365e45c8dd29f44631cf223bc5ef1cc1538e0ffbb1b616c8740fa35c26a
- request
- 565b761dec6ceb5932b135f6a6e71d39370e09da6d454c04b93c4156aacffd95
- transaction
- 3ca146740e3dc7866b604fcf278a34a837787ce3bc960ca38c88b98e2992b6eccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1665
the chainentry 1665
- sealed to the entry before
- 6476e72d52882adc5407d751c5e803980a28119f860408580a9f4c2f858c74f0
- this leaf
- bdc7bfa8ddb61163cc094f73f16cc96ee02b271f8da98b78c8ae9118cf007985
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OnSF3DQHohwzb7gJKBGmcwCKcXnuuRkPMsPOKupkZ0nu2dGou5EPtc1lQNsXCigWQYFwX14NPDEKci7X2+AhDA==