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
- 201fa5d724f86d74234f8f3e140d8165c32b34f90f42795946409d1ed3c0402f
- request
- b49c8522444692afb349bc73c1aa829cf5fc70d4bb5ae454da8a4b6515d403d3
- transaction
- a58d8bac7187a0ed54be193390309ec1e3bb30188d751d5bcb8a8181f3a8d910computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70118
the chainentry 70118
- sealed to the entry before
- 0a11fd0d7e5f768521dea02b59b87a61ae30e40091fc17f066acc70be74293bd
- this leaf
- 028b66bdf9a2cc396efd9f49f03205d0bffe5b5a59120db53bbe1006591621ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- enBg/I4R/vZInf+EB9X1zLKUX+NeEsqyftnUQxQ/OZ9MiqLcgrY4pdlj2Lu9Fb1TgZ4sSqiGwFtzu5DG4V0KCA==