Hey Ding Wei, I spent an hour to try to break something by using Chinese business objects and i failed. In other word, no big problems.Assuming the project team and the customers/end users are mainly Chinese, you should definitely try to use Chinese business object, since it will save you toons of time by reducing a lot of translations.
For instance, in a coach, you can just drop an object(in Chinese) and it automatically generate a view with a correct label (in Chinese).
For the developers who are less fluent in English, its clearly he/she can do the coding faster.
To be honest, "支付类型" is much more readable than "paymentMethod". Btw, also no more discussions about the camelCase.
But still I see 2 potential practical issues: A: language issues when cooperating with international colleagues who can't read/type ChineseB: still need some translations when integrate with other systems without unicode support
And last advice, before you decide to go for the Chinese BO, do extensive testing.