Web Services/Resources

SLIM CD provides web services and web resources to handle all aspects of payment processing transactions.

  • Direct Web Service APIs
    Perform transactions for credit, debit, check, gift
    Signature/Image/Receipt storage and retrieval
    Pull Reports from our servers
  • Hosted Page Web Resources
    Secure Sessons that control Payment Pages hosted by SLIM CD
  • JavaScript for pages you host
    Incldue our JavaScript library to keep your pages out of scope

Each of the above items is available as a .NET web service or as a web resource.   Each web service or web resource is also wrapped inside a library in a variety of languages. You can call the web services directly as a discoverable web service (WSDL), or you can perform HTTP POST. If you prefer to avoid that level of detail, you can use our libraries that wrap the calls for you so you only need to set properties and invoke methods. Either way, you can access all of the benefits of our web services and web resources. See the Class Libraries for more information.

The various technologies identified above can be used interchangeably so that the developer can mix and match solutions to best fit the individual implementation needs. For example, you can start a transaction using JavaScript to create a token, then actually charge the card.   Or, you can have the Hosted Payment Pages charge a card the first time, then use the token returned to bill the customer each month.

We recommend selecting your technology approach (direct API connections, Hosted Pages with Secure Sessions, Your Page with our JavaScript, or Launched Apps). Once you decide how you wish to take the initial transaction, then you will have inherently selected which initial web services/web resources you’ll need to use. Note that you may still benefit from using the other technologies or features for other parts of your application.

Our flexibility allows you to identify the best way to reduce your PCI scope through selecting the optimal technology for your situation. Once you’ve done that, you can use our standard API calls or libraries to perform subsequent transactions, pull reports for reconciliation, download signatures, and more.