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
- a2ccb5ecfa9594b7451e6c7a9764170019d59dc46907ff2c9cf4039be6703c87
- request
- 62cf914891043a75070de70d5cecd75c15372a181cf90bbaf568e48e409cfbff
- transaction
- be932260e3ffab1afe64d0bd99aba46c3dc9f20a43a5b760d2e03de3ca2f184fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38338
the chainentry 38338
- sealed to the entry before
- b2fecbd8a1b2ca9daf60cb55300628dacdeac3402f9b1d920e9ae8c2aa6b076c
- this leaf
- 7ebbebf666de323c2b1075c0ec7c06dab8b4464ee3c265c2b19a7ec39db4ea74
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HPatgnHxP2vFzRs0Stda5D67JiEt8M5D1xnWy7vle/8BhRRck+aG32puKk6sHee0QQq4q3Pws+Jg9cVVFr6yCg==