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
- 9416ed935781cbef2f3b44abbc1fd4abd9d798bd3ae1f72529fbec585bcaef69
- request
- fcf587ed5109a0e871242005caa76a1ad20b53f17035e90f99b598cd4eeb11ef
- transaction
- 4ddcad6e286eb091dfea8bac015448f16b85a4fe462caf62a47aa7b4eca2a856computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 696
the chainentry 696
- sealed to the entry before
- 0b6350af63e0bd4867d83fd34b51bcf8c3b3755b3758e6c8b7e43dccbed3b624
- this leaf
- f08c41926637199cbaf9b822c1154588aabd090afd216f624d48c5b8b9a6ce02
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +RKtn5jgG4DnBQjKefP0SB8XP8GK9KbhPgeG1ca5GVrPgsQavbEK95g0mV0YNIL9bclxqFiPb2mJVyOdXTmlBw==