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
- 02cf63d1aa60682c86cb9bb225adbc1eaab3037e3404f063a2afb1f9873ee778
- request
- 227ad338cedec9db9d1d6da2f177cdf58ed48920cb13ca3d772b69a9e3927a04
- transaction
- 2b65fabf1a3837733f5a77b79f800844c82979a0c518fc97dddfcc43f8f53c42computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65719
the chainentry 65719
- sealed to the entry before
- 8cb10765f94aa50997338cb54d56fb46630df6908fafa47269e7b93ad21181ff
- this leaf
- 0f7d7371ac85f67789260318bd2efddb55c79a4e0e7a8de6ffdb16b8b9451be3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wUGAVgFJGDittx+vcnxVUDlPq1B/d7R8dyZR4qjrutJhjiS43Z7bjDmEa+1/1EOnZeB16lWzKkH57DUmLvlQBQ==