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
- ca843cd72d63b397accdc0e87ea9e83933a694a368cc31dd05a366ab6ea21c0d
- request
- 3580a8ab493d441e0a55261e1bd3298ef87ab9d25e2e940aaa6a701899af3693
- transaction
- 1c1e97e56931843d85ae7a0efde78d17756878db51146831d5e7ed39cdf242d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 621
the chainentry 621
- sealed to the entry before
- 43d45775006bf71aeeb0d54b42732cd2148d1f9dcb41581bf5527e00ed64dfed
- this leaf
- 7c197bc40a109d584e233cf91d952af55d9db1d8a6d174055df135588b20b584
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EaJv7Viyl4dBGrxdICC7dnO6D6JaW2DIt7vg/1lUaBzPJCEBnQmxbRT1cXieoDT+vbRYFOKpUgE1R2QO3q3MBQ==