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
- 1ff6d1cbb7973285a8f43d6100200bc26ccd6490e1cb9c81034779e850d99595
- request
- 87c070d8ad29b32f2277df74b73d2238a9e70dc9353442dd13501a8e40f115cf
- transaction
- 3a9d0c1f652d599801b0a2d886f9c3916a60d37de62ca1b4607a81d8dabe73b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24242
the chainentry 24242
- sealed to the entry before
- 8f036c192d2b91e4b5e0971b3a52bf36b7ce0c5a7e803e71120e5e66d9827fcc
- this leaf
- 4c29528de33de4ba1a9fd982f9a3f186de792a152af2ffd70daf646d7a4b9f07
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t0+P60JVF/zSuQD6GYrLCIA+tWJ2S3HJu8/T8RtdZDMJkemzYSfTObVXm1Bp/Di0u0HLclyn6VQUnaAUM90pCg==