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
- ce58f44e0ee6bc05b08f85ac90c57be09bfb86d1f86b5b73c966700b420723c5
- request
- d1f807beba8803dc59cb095ff7301c93691bfb995b1a06e2331e4a251113a2e4
- transaction
- 4c4d9cde05a2ba6ca48d56e1c8466725b673d2660b89dbc922db351e9d0a9bf4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47023
the chainentry 47023
- sealed to the entry before
- 7c007f3df1eb2ea64ca46b6cc212de7641a37c213290c2782fbda2dd233086eb
- this leaf
- beb397edf7e20fd83392d6141badb913ed7b008a12eea659534cb8a77f57b48e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6uk5OHzYiG9cauYzlK+dei8XmvWgyxFwUYpcKDddnd7q3LsrT03i7YZE3HcVTz/EHNUlQ6EZyW14bic6YB+KDw==