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
- 9da7915a5774ee2a24a655d56dbaf1cc54173ba355d3c427c0b6987bd2bf89b1
- request
- 53046b756827e13916ae332170fca0fb42a7357982f6fbdca2687461fb3bd4f8
- transaction
- 1bcee0f9e0c9bc811ca34e087bae2b41e77f971458eed442e0987ca509c760cdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47415
the chainentry 47415
- sealed to the entry before
- 5e40becaef66771211d46d83c4b9ff03add4019ef374ddd7729ca60b766c19a7
- this leaf
- 763320a72c7e27c8a23dab9a0068a8f3c3253000850707cbe798fd467d87e4ed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G9clV2Ilq89PCSRkRhDW/QvbIQljE7BCc2cRTOw38fvoS+hEfSU0Xv15mYPBA3n+JeQaVJGMa1ZZ8Rrig/SBAw==