square has recently sent out an email to customers using square in japan. apparently, in japan at the end of march, you will need to follow the emv 3-d secure guidelines.
see this link on the square website.
now, here is where square makes it confusing. they talk about a new payment flow (currently in beta) to help implement the emv 3-d secure guidelines.
but if you read the notice, it clearly states,
“…Web Payments SDK and Payments API will need their apps to support buyer verification.”
the new payment flow is not required to implement the emv 3-d secure guidelines. the existing payment flow, as implemented by my module, already supports the emv 3-d secure guidelines.
the existing payment flow has a method called verifyBuyer which implements the emv 3-d secure guidelines.
in fact, emv 3-d secure is already required in the UK. my UK customers are processing credit card payments without problems utilizing emv 3-d secure.
so, to answer your questions with regards to emv 3-d secure, YES, my commercial module supports the emv 3-d secure guidelines.
purchase of my module also includes updates for 1 year; and if during that time i decide to implement the new payment flow, you would get that free of charge.