I changed the way i triggered the payment system for Tokens with eWay due to the SSIS 2005 limitations and the fact that i don't have SSIS 2008.

Instead of a SSIS package, i created an ASP.NET processing code-behind page using eWay Token Payments Web Services.

I did a combination of SQL datasets and statements for INSERTS/UPDATES using TRY/CATCH blocks and a number of other ASP.NET techniques.

The long story short is that i had to develop my own VB scripts to do all the processing online based on various triggered events.

I suppose i could have moved my ASP.NET code-behind script into a SSIS package Script Task and then called it by passing in all the relevant parameters, however everything became a lot easier to do it online in the web page.

If i were creating a backend batch payment processing solution then i would probably go the SSIS route. This way everything could be hidden on your server and be invisible to the web front end. This way you limit the amount of security controls you need to build into the ASP.NET webpage for authentication and credit card processing prior to submissiion.