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
- fa6ca0ad8005d1f4c9ece7151545042f467f20c3705464dfff338c684d32605e
- request
- 033de8176d8ebc91c60c361275b4d36f19ac467e101f168959838f2bab8d8ea0
- transaction
- b614d21d8a2c6af67f8095eeda574da4ccb2a41a565dcedc1076d2db107bd14ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21079
the chainentry 21079
- sealed to the entry before
- 8fabb805b0ef45b543249288d6fa24b9d92b1ac8f78d438f895d038623371ea2
- this leaf
- 6c5e442d224184ff50434708ff7af2881eea4680515764dfa6d057d7983b4172
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jh0MINfX0BBw9dRTvFR1CXZ8laTIMDgK+Hnvfh9uh8e5g4uhLwadICSg5k47fBe2WQ678FXrVBxtb5NC4ZCMDg==