Use Customer Credit
Learn how to use the Digital River Customer Credit extension.
Last updated
Learn how to use the Digital River Customer Credit extension.
Last updated
You use Digital River's customer credit feature to enable a number of different storefront customer credit functionalities such as gift certificates and rewards points.
The SFCC platform does not natively support gift cards or store credit functionality. This functionality is provided instead by 3rd party integrations. Rather than integrating directly with these 3rd party options, use the Digital River customer credit cartridge to provide several functions that make the necessary calls to Digital River to support this functionality. The back-end implementation of the customer credit functionality is provided by the int_digitalriver_customercredit
cartridge.
You are responsible at the time of implementation to code necessary changes to the Customer Credit feature for your use case. You do this to call the functions provided by the DR cartridge that is needed to connect to your 3rd party integration.
Read the information in this section to learn how the Customer Credit cartridge supports the customer credit feature. Use the suggested customization steps to integrate the customer credit feature for enablement in specific use cases.
In the following example of the cartridge customer credit functionality, the GIFT_CERTIFICATE payment method and the BASIC_CUSTOMER_CREDIT payment processor on the SFCC side are being used.
If you use the customer credit cartridge as demonstrated in this example, first make sure that the specified payment method and payment processor are set for the customer's site.
Use the information that follows to set up the integration of the customer credit feature with an example payment method.
Note: If using the cartridge for integration with other customer credit use cases, make sure you apply the appropriate method/processor configuration to meet the use case.
First, use the following steps to configure the payment method and processor in the Business Manager.
In the Business Manager, go to Merchant Tools > Ordering > Payment Processors and ensure the BASIC_CUSTOMER_CREDIT payment processor is present. If using a different payment processor, complete this step according to the use case.
Next, go to Merchant Tools > Ordering > Payment Methods in the Business Manager and ensure the GIFT_CERTIFICATE payment method is present and enabled. If using a different payment method, complete this step according to the use case. The BASIC_CUSTOMER_CREDIT payment processor is selected for this payment method. Select the payment processor from the previous step.
Note: All line numbers referred to in the following code samples and example screenshots are relative. For the location of the code changes being discussed, refer to the highlighted areas in the screenshots that are isolated with a green or red border around the code.
Digital River provides three controllers in the cartridge to integrate the backend part of the customer credit feature. These are the following:
Use these controllers to integrate customer credit functionality into your storefront. Read the next sections to understand each controller and how it is used.
Use this controller to make an API call to Digital River to create a customer credit source, attach the source to the current checkout, and add a customer credit to the current basket as a GIFT_CERTIFICATE payment method.
Modify the code as shown in the screenshot below to create a new payment instrument for customer credit depending on your implementation of secondary payments.
Script path: int_digitalriver_customercredit/cartridge/controllers/DigitalRiver.js
Request type: POST
Request body schema: application/json
It is expected that the customerCreditAmount
parameter should be less than or equal to the amountRemainingToBeContributed
value on the checkout. The value of the customerCreditAmount
is checked to ensure that the amount matches the criteria before making a request. In the case where an amount greater is sent, a response with the error message will be received.
Pass the primarySourceId
parameter in case the primary source is already attached to the checkout.
Prior to calling the DigitalRiver-AddCustomerCredit
controller, make a call to the DigitalRiver-CustomerCredits
controller and obtain amountRemainingToBeContributed
and primarySourceId
from the response.
The following is an example of a response you might receive after a successful call:
Response body schema: application/json
The following examples show error responses you may receive after an unsuccessful call.
Invalid credit amount - The following is an example of an error response for an unsuccessful call involving an invalid customer credit amount.
Status: Error occurred due to an invalid customer credit amount.
Response body schema: application/json
Credit source creation unsuccessful - The following example shows an error due to an unsuccessful attempt to create a Customer Credit Source.
Status: An error occurred creating a Customer Credit Source. The creation is unsuccessful.
Response body schema: application/json
The following parameters describe the response schema for errors
Use this controller to delete the customer credit source from the current checkout and remove the customer credit from the current basket.
Script path: int_digitalriver_customercredit\cartridge\controllers\DigitalRiver.js
Request type: POST
Request body schema: application/json
The following example shows a response you might receive for a successful RemoveCustomerCredit
POST call.
Status: Customer Credit Source removed successfully.
Response body schema: application/json
The following example shows a response if an error occurs removing a Customer Credit source.
Status: Error occurred removing a Customer Credit Source.
Response body schema: application/json
Use this controller to retrieve actual information about already applied customer credit sources, primary sources, and some total amounts. For example, you could use this controller to get information before adding new customer credit sources.
Request type: GET
Request body schema: application/json
There are no request parameters required as SFCC automatically tracks the current cart object which has all the information needed to execute the request.
Request example: There are no parameters for this request so an example would consist of an empty payload
The following example shows a response you might receive for a successful CustomerCredits GET call.
Status: Customer Credits information has been retrieved successfully.
Response body schema: application/json
The following example shows a response you might receive if an error occurs retrieving CustomerCredits information.
Status: Error occurred retrieving CustomerCredits information.
Response body schema: application/json
Parameter | Type | Description |
---|---|---|
Parameter | Description | Type |
---|---|---|
Parameter | Description | Type |
---|---|---|
Parameter | Description | Type |
---|---|---|
Parameter | Description | Type |
---|---|---|
Parameter | Description and Type | Type |
---|---|---|
Parameter | Description | Type |
---|---|---|
Parameter | Description | Type |
---|---|---|