Service Virtualization

We need to virtualize payment partners accessed by our Payment platform.

However, some Payment partners are just acknowledging the good reception of Payment Platform inquiry and then initiate another transaction to update our Payment Platform with the status (few seconds afterwards).

So after sending the reply, we must initiate a request from DevTest (we can ignore the reply from payment platform)

This tie-back process is kind of standard for Payment business: any hint on best technique to implement this with DevTest ?

There are a few ways you could handle this in the product depending on the protocol.  There is an option to have multiple responses for a single request for messaging based protocols - in this case you could have two responses for a specific request in your service image and then return a status message followed by a secondary reply.  Alternatively if it's a protocol like HTTP, you could customize your VSM file by adding a step after the Responder step in order to send another message out after the virtual service responds.  You could use a script to add a delay as well if you need to simulate some wait time in between.