This is an old revision of the document!
TWBS CC Web Order Import Integration Information
The purpose of this section is to provide information on how to populate user defined fields on the SAP® Business One Sales Order marketing document header at the time of import. These authorizations, performed by an external system using the credit card gateway account assigned for TWBS Credit Card processing, can then be settled inside of SAP® Business One.
TWBS Credit Card Processing will only be capable of creating new authorizations in the case of an expiration of the original authorization or an increase in the document total above the original authorization amount if the customer profile ID and payment profile ID for the card on the transaction have been imported. If they have not, then we cannot reauthorize if the original authorization expired. If the document total has increased above the original authorization amount, any amount above the original authorization amount will need to be paid in a separate transaction.
The import user defined fields have been moved from the marketing document lines to the marketing document header in the 1.5 version of TWBS CC Processing. There are also new user fields that didn't exist in previous versions. Any web integration data mapping that was used in previous versions of TWBS Credit Card Processing will need to be re-mapped for the new user defined fields. Please use the information below for remapping.
The external application performing the initial card authorization must be using the same account credentials as those setup in the TWBS Credit Card Processing configuration screen. If the gateway credentials used in both places do not match, TWBS Credit Card will not be able to settle the authorizations.
The Web Order Import data integration for TWBS Credit Card version 1.5 does not require that any information be encrypted for import.
The Web Order Import data integration for TWBS Credit Card version 1.5 is only designed for the importing of authorization transactions that have not been settled at the gateway. This process will not work if the authorization has already been settled by an outside method.
| User Defined Field Name | Data Type | Max. Length | Description | |
|---|---|---|---|---|
| TWBS_CC_TrxType | AlphaNumeric | 10 | Payment type for credit card orders. This field should be populated with the value “CCWeb” to identify that this order and authorization came from an external source. | |
| TWBS_CC_CustProfileID | AlphaNumeric | 20 | The Customer Profile ID value from the gateway of the business partner associated with the card used for the authorization transaction. | |
| TWBS_CC_PayProfileID | AlphaNumeric | 20 | The Payment Profile ID value from the gateway of the card used for the authorization transaction. | |
| TWBS_CC_CardLast4 | AlphaNumeric | 4 | The last 4 digits of the number of the card used for the authorization transaction. | |
| TWBS_CC_CardType | AlphaNumeric | 30 | Type of the card used for the authorization transaction (i.e. Visa, MC, etc.) The value filled in this field should match a valid value in the Credit Card Setup screen in SAP® Business One. Note - The value imported to this field must be the Name value, not the Code value. This screen is located under the Administration Setup Banking Credit Card menu option. | |
| TWBS_CC_AuthTotal | AlphaNumeric | 15 | Total amount of the authorization transaction. This amount should be rounded to 2 decimal places. Note - The value for the authorization total does not need to match the document total. However, if the authorization amount is less than the document total, the remaining balance will need to be paid though another transaction in SAP® Business One. | |
| TWBS_CC_AuthExpDate | AlphaNumeric | 10 | Expiration Date of the card used for the transaction. The formatting of the data in this field must use “MM/YY”. | |
| TWBS_CC_TrxID | AlphaNumeric | 15 | Transaction ID Reference Number. This is the transaction id # returned by the payment gateway. Usually an 8-10 digit numeric value. | |
| TWBS_CC_AuthCode | AlphaNumeric | 15 | Authorization Reference Code. This is the authorization code returned by the payment provider. Usually a 6-8 character alphanumeric value. | |
| TWBS_CC_AuthDate | AlphaNumeric | 10 | The date of the authorization transaction. The formatting of the data in this field must use “MM/DD/YY”. | |
| TWBS_CC_CardAddr1 | AlphaNumeric | 30 | Address 1 information of the card holder of the card used for the transaction. | |
| TWBS_CC_CardAddr2 | AlphaNumeric | 30 | Address 2 information of the card holder of the card used for the transaction. | |
| TWBS_CC_CardAddr3 | AlphaNumeric | 30 | Address 3 information of the card holder of the card used for the transaction. | |
| TWBS_CC_CardCity | AlphaNumeric | 30 | Address city information of the card holder of the card used for the transaction. | |
| TWBS_CC_CardState | AlphaNumeric | 30 | Address state/province information of the card holder of the card used for the transaction. | |
| TWBS_CC_CardZip | AlphaNumeric | 10 | Address postal code information of the card holder of the card used for the transaction. | |
| TWBS_CC_CardUID | AlphaNumeric | 50 | A unique name for a payment profile stored on the gateway associated with the business partner. An example of this could be the card type and the last 4 digits of the card number (“Visa 1234”). | |
