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
- 1e35ddb74abb0f6aa1b04eaddf0541ae2a59031c17ee31801872690e64b5ca6d
- request
- d1715f11e76768ff57e0ec5568db3e3a26f742839b9790606b0138c085c5706f
- transaction
- 75451404660c6025ae3a8705817c4cfcbaf9812c80c1b7c135ac45673287984dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10632
the chainentry 10632
- sealed to the entry before
- 901974a3cb2aa0b4a487aa08f282b2ea79e964820ff94a402a1d47efd24449a9
- this leaf
- a323b685a7b49a70bf088d9fe761aa1a5a3c0d5f42bd13e44ca094ebc25bfbb6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JpaKZI4x67PpPn1+ygTeXebPpDhY5Eg43f2s7XaL6FPZtCUaTP1p8hTkVvcj/1BS1x/qqRYtlozDbI93t5G7DQ==