If within the same system, you have multiples of "personService", "paymentService", and none them have unique features that can be used in the name, then you probably have a design problem.

Qualify the duplicate name with why you have a duplicate.

Already have Service and need Service? How bout NewService and Service instead. Or ${NEW_TRAIT}Service and Service. (can replace Service with any domain)

You could also just not duplicate and keep a single Service. Like other mentioned this is likely a design problem at any point names clash.

When faced with the same problem, Elon went with X Æ A-12.

Personally I prefer UUIDs for global uniqueness.