Yes, the names and the PNR move across on their own, so for a normal booking you do not need to email the seller at all. When your engine blocks a seat through the eazyPNR API, that hold sits against the seller's block with the same dates you can see on the listing, the name list deadline, the release date and the ticketing time limit. Your engine then passes the passenger names in the same call or in a later call, as long as it is before the name list deadline, and the seller sees those names on their side straight away.
Once the seller or the airline issues, the PNR and the ticket details come back to your engine, so your staff and your customer can see the live status without anyone chasing it. That means your booking engine can hold the net fare you have from the seller on your side, apply your markup, show only the agent fare to the buyer, and still carry the airline reference through to the voucher or the ticket you send out.
Two things are worth building in. How quickly a PNR appears depends on the airline and on the seller's contract, because some sellers issue as soon as names are in and others issue in a batch nearer the ticketing time limit, so your engine should display the real status rather than promise a ticket the second payment goes through. And since name corrections after the deadline depend entirely on airline rules and are sometimes not possible, put a check in your booking flow so names are captured exactly as in the passport. A wrong name caught late is the usual cause of a reissue request or an ADM.
The practical next step is to register on eazyPNR, look at the live seats and the deadlines on each block, and run one test booking through the API end to end before you open it to your customers.