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
- 606503d7fd2805eb2d9e202fb0eecfb5ee0ee14da04e674e3124c43060c1de6c
- request
- 41a67cc66323e9b309a8ee05af24e69769c5be037efdf44cc51f846285b4cc3c
- transaction
- 443befeb09407d99d5e1cbbbe8a47e697e23052f6effc789c9776fe13e194ba7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35612
the chainentry 35612
- sealed to the entry before
- fb1cd4ac2059902a2ee1340457f8bb8361bafefb5fec5ac84702237bcbe838e7
- this leaf
- 0e48e4d5c064b713324733ea643454bde2a4642a1273dd3b2f6f9de9ba8aa375
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OaghSKuKYmVO8cgKPbi2MBqomAZXXLT8ShyuheAVcVBH4Wyc6mwRBecC0trtCdD8nsco8MyvskJObXkDFLHdBQ==