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
- ec8f9499dfef29e0d2ab691fe5d93f160be9d5e22963d5a9b8f061bfe7a5f6a3
- request
- 321c012b50a797e7354193982f3d2d869e11b635afaf0454c236df6e2a5fc394
- transaction
- 83f9436954751dd75e1fb5af82dc608c3932e1136fe0287bb7ff4f0197e8848ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2075
the chainentry 2075
- sealed to the entry before
- e1bb709a2e1a6a486cc9d8de5a309808e2f5b0f65f99ff696dcad40e17c1752a
- this leaf
- 3f41f0586cecfebab06f2a00502359c82964c3f691fff2d4f07fdf261822095e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /Dc50K1xqiUsR6CGAWe33/EQApAy5DPPuZXrFoYj2jYxkAup7YvxX5WLdRhZhfqdU4elyRdIa2LITDrZxuFFBw==