The Enhanced Digital Suite (EDS) facilitates a full-funnel pre-qualification and checkout flow merchants use to offer customers the ability to check out with Installments, Buy Now Pay Later (BNPL), or Card products. EDS seamlessly integrates throughout the customer’s shopping journey to enable higher purchasing power and drive conversions.

In the EDS modal, sensitive customer information is collected in a secure iframe and sent directly to Bread in encrypted form, never touching your server. The EDS SDK is a JavaScript snippet you will add to your site, and it provides the functionality described in the rest of this document.

How it Works - Transaction of Data

  1. The customer clicks a financing Placement to open the EDS modal and initiate the Installments, Buy Now Pay Later (BNPL), and Instant Credit flows.


    1. After a customer is pre-approved, the customer can complete the installments checkout flow by clicking the final “Accept & Check Out” button. This generates a pending transaction with ADS.
    2. The SDK emits an INSTALLMENT:APPLICATION_CHECKOUT event containing the applicationResult for the customer’s checkout. Merchants can listen to this event by configuring the on() method of the SDK. The applicationResult will include a transactionId which is used in the next step.
    3. The merchant will pass the transactionId contained in the applicationResult to their server through a callback function contained in the SDK’s on() method.
    4. From the merchant server, the customer’s order should be created in the order management system and validated through a series of requests to the Bread REST API.
  1. CARD Flow
    1. After the customer completes their CARD application, the SDK emits an CARD:RECEIVE_APPLICATION_RESULT event containing the callId for the customer’s application. Merchants can listen to this event by configuring the on() method of the SDK.
    2. The callId is passed back to the merchant’s server (or Token Provider) through an AJAX call in a callback function contained in the SDK’s on() method.
    3. From the merchants’ server (or Token Provider), the callId should be used in a request to the ADS REST API to retrieve account details.
    4. The REST API will return the account details, which include the account ID. The merchant will retain the credit information until the customer completes the checkout process in order to prefill the checkout detail.

What’s Next