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
- 34308090aa885ca49f89d7e8244c25fc02489ae8ecdc1b10a0f929dfa804bc2b
- request
- 8df8b279633c926d68505ff4428801b17761321dd3d07db4b4bb6130618e64c5
- transaction
- 0f23e600c34c4a00c1fd5e3a96ece40fd91d7c2572a9d50f7f6661440de5c089computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66416
the chainentry 66416
- sealed to the entry before
- a2f25dcb0309c436d8f0456c374d643bc7319e169e023fd618c986e4900a14f3
- this leaf
- 0aecd3038e20c91e2dd1103d14c5a9c2d6d5ff419035970510d5207f6b94471d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- giLjpOteQmB0jsOpdaj4XZHhCd5vREN/Nykz137xKinTcVqrm3UukOBp9CW97pd7M4VbNJuCzIonD+rMIjPJBA==