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
- 9dc0973e0710ee7436624352585a2f903cc11e471fbb3dff00688af07d4a4819
- request
- 385fcf14ee3f2e6791620eb91034fcb83d655481a874a58ae97f0e6bd1881772
- transaction
- 9d17e238868ccd8a6c031e753d26683b2685c68119d30690f8bbd45ef0ae27cfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73894
the chainentry 73894
- sealed to the entry before
- 393e3c238e71536b2af38e6a9376b11be8ceda7cded9cb8f0cb586f18529f22c
- this leaf
- f3f23072c1f29614e319512d3fdea4da97772aab9303cc46feed940fa311d695
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 97Y3VXRGE2Ra1GqJZ7M9Fpe68ZBv7kAyPPfcXv2wheOihHomHtDIPVKkpyy5ikg6dQLTTdteWs6+Fi/1TqatBA==