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
- ed586dba281977229432e7a02bd21444cef06eaf6f23968f212de7723808bf7f
- request
- df034004390b5ec679fb2dd3f2ed9ac5b4b96f8c2dcf4d747b08626c564126cb
- transaction
- 25f1d57429589d3fa49d283c0edca8c91fb55162f791132dffff630f5a2f73e1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1335
the chainentry 1335
- sealed to the entry before
- c7a1d10b15ee08630088619e7f825e155d3add3736f2ce8997a3fd2965a7b13c
- this leaf
- 762a23a6bed1148a55deaf28952d0bb7eebdbdee35aef95f4655fc6e7b4983ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- chbcspo34pmy9QN3UWi0sefpiFFJU/HOmkQy+waVClr/mtkm0y7rw2h6WF7enCWAcKEFs0r0qF6UHVVAlJC7DQ==