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
- 0a2f04495a9508aeeb1e1985ec224941968c4ee21eb0fea6aa8bb95bf67bc52a
- request
- 16afdcf3c156e96e395abef822f75cca9298ffc748cb24440810b5accb72745a
- transaction
- 85ed9539facf7513d8a60d91bfa1bfb619dcf19e5105b8cf90f2702c0da88bdecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23639
the chainentry 23639
- sealed to the entry before
- 9652a877fb4efc30c5c80f2d0813c2429820e90e2d61abac3f16ea1dcc4cac09
- this leaf
- 05a7c2188e9b88f08ad635e269763de20b5372e2c4cbbec682faf44c9eeed5af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +S/CujHhcasK/4sdNY4vwlUnCyNp0/NwOo4p8WUWC1nJxS+r/YmJmdeZodinqFTbc6u6WlQgboBk8/Uz5xz2Ag==