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
- 3bab41ae5090b1ca8b2fda5493bcaad052e19ed85c3ee5059e941babd3570771
- request
- e1fc935c475b948932b17851d4499a775d62528f55b824a28ac511d552d0becb
- transaction
- a5d0dea71b6b594f0d40497b310e470a34769c94c52dc8dbf944d6d52dfd856fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62761
the chainentry 62761
- sealed to the entry before
- 26111f20b26f2e611fc3c1be154fc2375271231db8d5a22013797cf31c58588e
- this leaf
- 82df82a789291c38f87c76c3fb7a8a1dceefe6c3590c4f502bc13c8fd0288da8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SR3Tz0ekLNrCUOUkIv4IiGRsSp8TOQOSVT2MOQQi54a1hjERhTjRhT0Kgax+v4oQ5Iz53yIb9AK8mHG63yyQAQ==