The diagrams and instructions below outline how to integrate the Forter cartridge so that you're able to send information about the PayPal account associated with the customer or transaction and receive a real-time Forter decision.

When integrating with Paypal, we recommend modifying your Paypal Cartridge settings. To do this, go to:

This will allow the Forter cartridge to receive relevant information to decision whether a paypal transaction is captured or voided. Please note we do NOT handle Billing Agreement checkout flow in this example.

The Express Checkout should include Authorization before Forter is called. This can be done by setting the Payment Action to "Authorization" or by setting Run Authorization in case of Order to Yes.

make sure the Paypal cartridge is set to send to Salesforce Commerce Cloud the billing information. Please note this configuration may need external permissions added by Paypal support to your Paypal account.

The diagrams below are from the PAYPAL_EXPRESS-Authorize Pipeline. After the CommitTransaction is called Forter requests additional information about the transaction from Paypal by triggering the Paypal-GetTransactionDetails API call. After the details are stored Forter API is called in order to provide a decision on the order.

The diagrams below are from the PAYPAL_EXPRESS-Authorize Pipeline. After the "CommitTransaction" is called Forter requests additional information about the transaction from Paypal by triggering the Paypal-GetTransactionDetails API call. After the details are stored Forter API is called in order to provide a decision on the order. Based on the Forter Decision and the Forter Cartridge configuration, additional API calls are made to Paypal in order to capture or void the order as needed.

Based on the Forter Decision and the Forter Cartridge configuration, additional API calls are made to Paypal in order to capture or void the order as needed.

1) Assign Node **isAuthorized**

Add an Assign node. Set _From_0_ to true; _To_0_ to isAuthorized.

2) Add a Decision node. Set **Decision Key**

Add a Decision node. Set Decision Key to:

3) Add Assign Node **DoAuthorizationResponseContainer.data.transactionid**’

Add an Assign node. Set From_0 to DoAuthorizationResponseContainer.data.transactionid; To_0 to TransactionID

4) Add Assign Node to transactionID

Add an Assign node. Set From_0 to DoExpressCheckoutResponseContainer.data.paymentinfo_0_transactionid; To_0 to TransactionID

5) Add Call Node Paypal-GetTransactionDetails

Add a Call Node Set Pipeline to Paypal-GetTransactionDetails.

6) Add Assign Node in PaypalTransactionDetails

Add an Assign node. Set From_0 to GetTransactionDetalisResponseContainer; To_0 to PaypalTransactionDetails

7) Add Script Node to ForterCallStoreResponse.ds

Add a Script node. Set ScriptFile to int_forter:pipelets/forter/ForterCallStoreResponse.ds; PaymentInstrument to PaymentInstrument; ResponseDataContainer to PaypalTransactionDetails; ResponseType to paypal_transaction_details_response.

8) Add a script node to ForterCallValidate.ds

Add a Script node. Set ScriptFile to int_forter:pipelets/forter/ForterCallValidate.ds; Order to Order; JsonResponseOutput to ForterResponse; PlaceOrderError to PlaceOrderError.

9) Set Decision Keys

Add a Decision node. Set Decision Key to

10) Set Additional Decision Keys

Add a Decision node. Set Decision Key to

11) Set Payment Status to Completed

Add a Decision node. Set Decision Key to:

12) Add Assign Node to update payment details

Add an Assign node. Set:

**13) Add a Call node. Set Pipeline to **Paypal-DoCapture

Add a Call node. Set Pipeline to Paypal-DoCapture.

**14) Set ScriptFile to **ForterCallStoreResponse.ds

Add a Script node. Set ScriptFile to int_forter:pipelets/forter/ForterCallStoreResponse.ds; PaymentInstrument to PaymentInstrument; ResponseDataContainer to DoCaptureResponseContainer; ResponseType to paypal_capture_response.

15) Add Script Node to UpdateOrderTransaction.ds

Add a Script node. Set: ScriptFile to int_paypal:data/UpdateOrderTransaction.ds; IsCustomOrder to false; MethodName to "DoCapture"; OrderNo to Order.orderNo; TransactionID to

16) Add some more Assign Nodes!

Add an Assign node. Set:

**17) Set Pipeline to **Paypal-DoVoid

Add a Call node. Set Pipeline to Paypal-DoVoid.

18) Update Void Response Pipelets

Add a Script node. Set: ScriptFile to int_forter:pipelets/forter/ForterCallStoreResponse.ds; PaymentInstrument to PaymentInstrument; ResponseDataContainer to DoVoidResponseContainer; ResponseType to "paypal_void_response".

19) Add Script Node to UpdateOrderTransaction.ds

Add a Script node. Set the following:

The Forter cartridge has built-in functionality for saving the PayPal API responses – the transaction details, capture, void, authorization and expresscheckout responses. The data is stored as a JSON string in the custom attribute of the Order Payment Instrument object. Each response is saved to its dedicated custom attribute. The recommended type for these custom attributes is Text since in some cases the response is over 4K characters. In order to save the PayPal response a script node must be added in the place where the required data exists.

For example PayPal transaction details may be saved right after a call to PaypPal-GetTransactionDetails and passed into the int_forter:pipelets/forter/ForterCallStoreResponse.ds script. In the script Dictionary Input, the “paypal_transaction_details_response” is actually the type of the response custom attribute, PaypalTransactionDetails. This data point is an object that contains information about the current transaction and PaymentInstrument is your current payment instrument.