I have been using the "Encyption with ASP" acticles by Julian Sitkewich with good results except with SOAP. It is a Vernum Cipher type Encyption where you use a key file and addition to create a new character no greater that 255. <BR><BR> We are setting up services using XML and SOAP. When I encrypt information on the server end, and wrap it in SOAP about a third of the decrypted info on the client end is corrupted. Basically the encrypted numbers become 63(ascii ?). Much of the encrypted string is unprintable characters but they are below 255. I wouldn&#039;t have thought this would have a problem.<BR><BR>Any ideas why? <BR><BR>Celeste