Sorta kinda. It's not just a fancy name, for one, but an entirely new way of defining types.
Interfaces in C++ are also far more limited than concepts. For one, interfaces only work on class types. Concepts work on both classes and built-in types (e.g. int, float, pointer types). To make use of interfaces, you must pass objects by pointer or reference, not by value. Classes used this way have to be virtual, which carries a performance cost. There's no clear way in C++ to state that an object adheres to both interface A and interface B: you'd have to create a third abstract interface class which inherits from A and B, and have your class inherit from this third class. Interfaces are also highly non-standardized, which would mean that in order for interfaces to replicate the functionality of concepts, library developers would need to come to an agreement on a common interface set and then completely refactor their class definitions to conform to that common interface set.
So yes, it is possible to refactor code to use interfaces and virtual classes everywhere to produce a similar design to the one offered by concepts, but it will require a lot of work, won't be terribly readable, and comes with a performance penalty.