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
- bbb0f133acbd128c9329ef6b0ad976c9a158a2faffa9a9bab20bd7c8d6116a98
- request
- 349fa99e2588111f03e80bf4fbeeca6cb745b0482ca2e98ecdc130b93f2ed67b
- transaction
- 5830e6f53ceeece171fd7ce0028e718c473ce8555bc605bfef86264fe640002fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7169
the chainentry 7169
- sealed to the entry before
- bc250f3f95123e1beea044f4bcd91513817ea98158338ab97970c76a137764df
- this leaf
- 49089c71e7682c3cac08881c483f79e24deea79738dc3e6f11e00b712ff64d59
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ows6gdXVhglHBbMpoiaS2JgCMtd/mkB0DFiIYCiKdNIfAf+zBihQy3MckyxmywsgqG8uSMTJYUaVOcH7tvCKBA==