This document serves as a comprehensive guide for migrating from iCheckGateway's SOAP-based API to Forte's REST-based API. It outlines the necessary steps, mappings, and examples to ensure a smooth transition.
- Overview of AddCustomer Endpoint: The AddCustomer SOAP method is used to save customer profiles and can optionally associate a tokenized payment method.
- API Details: The document specifies the SOAP endpoint, request parameters, and the required headers such as Host and Content-Type.
- Field Mapping: It provides detailed field mappings between iCheckGateway and Forte, including required parameters like FirstName, LastName, and EmailAddress, along with their corresponding fields in Forte's API.
- Transaction Handling: The guide explains how to handle transaction types, including voids and refunds, and illustrates the differences in handling between the two systems.
- Response Handling: It discusses how to parse responses from Forte's API, which is in JSON format, contrasting it with iCheckGateway's pipe-delimited responses.
- Testing and Validation: The document emphasizes the importance of testing in Forte's sandbox environment, ensuring that ACH details validate correctly before moving to production.
- Authentication Changes: It highlights the shift from iCheckGateway's credential structure to Forte's HTTP Basic Authentication using API Access ID and Secure Key.
- Notes on Migration: The document concludes with important notes on adapting to the new API structure, including environment handling and the necessity of re-tokenizing payment methods.