Configuring Konbini
Learn how to configure Konbini for DigitalRiver.js with Elements.
If you're using DigitalRiver.js with Elements, you can create a Konbini payment method for your app or website in four easy steps:
Step 1: Build a Kobini source request object
Build a Konbini source request object. A Konbini source request object requires the following fields.
Field | Value |
---|---|
|
|
| The payment session identifier. |
| An Owner object. When the
|
|
Konbini source details object
Field | Optional or required | Description |
---|---|---|
| Required | The identifier of the store where the Customer chose to pay. If you use the DigitalRiver.js Konbini Element, Digital River automatically populates the value for you. If you construct the request yourself, this is a required field. |
Step 2: Create a Konbini source using DigitalRiver.js
Use the DigitalRiver.js library to create and mount elements to the HTML container. If you are using the DigitalRiver.js element (option 1), the storeId
value is automatically populated based on the customer's selected store. If you are not using the DigitalRiver.js element (option 2), you must construct the request to include the storeId
parameter.
Option 1: Create a Konbini element using DigitalRiver.js functionality
The pattern for creating the Konbini element follows the same pattern as other elements and exposes the same customization and events. You can customize the look and feel through options and then place it on the page.
DigitalRiver.js will create and render a select element that populates with the store logo and localized store name of the available stores where the customer can pay using this payment method.
The same events and structures appear in the Konbini element, and you should listen to the Change event to determine when the user has made a selection. When the change event response contains "complete": true
, the shopper has selected a store.
To create a Konbini source, reference the created element and the supplemental data in your createSource request. DigitalRiver.js will retrieve and assemble the request on your behalf.
The address
object must contain postal code and state/province data that adhere to a standardized format.
Option 2: Using DigitalRiver.js to create your own Konbini display
If you decide that you do not want to use the out-of-the-box functionality provided with the Konbini element, you may also use the digitalriver.retrieveKonbiniStores()
method which will allow you to build your own experience.
Retrieving available stores
DigitalRiver.js exposes a method that allows you to retrieve the available stores where Konbini is accepted. If stores are available, the response returns an array of objects. If stores are not available, the response returns an empty array.
Retrieved stores
You can use the retrieved stores to build an experience suitable for your needs.
Once you reached a point in your flow where the customer has selected a store, you can use the createSource
function to assemble and pass the data to Digital River to create your payment.
Additional fields required: If you are creating a Konbini source without using the DigitalRiver.js Konbini element, you are required to pass an additional field storeId
.
Key | Value Description |
---|---|
| The identifier of the store where the customer will submit their payment. |
Step 3: Use the Konbini Source
Once created, the Konbini source will be in a pending_funds
state. Attach the source to a checkout. Once attached, you may submit your order.
The following example shows how to attach a payment method to checkout.
Step 4: After submitting the order
Once the order has been submitted, the source remains in a pending_funds
state. At this point, direct your customer to go to the store they chose and pay the invoice. These details are reflected in the konbini
block of the payment source.
Field | Description |
---|---|
| The customer's receipt number. |
| A URL that links to a printable invoice that can be brought into the store while paying. |
| The name of the store where the customer will submit their payment. |
| The localized name of the store where the customer will submit their payment. |
| The logo of the store where the customer will submit their payment. |
Last updated