FAQs

What is MoR?
Merchant of Record. The term “merchant of record” refers to the entity that is legally authorized and responsible for processing customer payments—including credit and debit card transactions and digital wallet transactions—for goods or services on behalf of a business.

What is SoR?
Seller of Record. The organization in charge of carrying out a sales transaction and supervising the delivery of products or services to the client is known as the Seller of Record (SoR).

What is the difference between Product and ProductLine?
Product Line is Brand. Product is a single item sellable item which is part of the catalog and belongs to a ProductLine.

Is there a sample for how to display Instructions on product page?
Here is a sample of redemption Instruction type, under "How to Redeem" for a Sephora card on Giftcards.com

How many currencies can be supported per Product in a Catalog?
Only one currency is supported per product based on product's country.

What is the difference between locale and locales?
Locale at Product level represents the default locale of that product. Locales at product level represents the supported locales of the product other than the default locale. There can be multiple locales supported per product.

Which product attribute translations are supported in locales?
Name Description termsAndConditions instructions

What are the minimum attributes required to place a single eGift Fulfillment Only Use case?
Order level: external_id sender object Order Line level : product_id quantity face value object

How can I retrieve eGift URLs in an eGift Fulfillment Only use case?
There are two ways to get eGift URLs: 1. Using GET API calls Call GET /v3/orders to retrieve the eGift URL for each line item. The eGift URL will be available for each line item once the order status is COMPLETED. 2. Using Webhook Notifications Integrate with BHN webhooks to receive order and line item status updates When you receive a COMPLETED order status notification, use the GET API to fetch the eGift URL Webhooks help reduce unnecessary GET calls. For more details on webhooks see - https://developers.bhn.technology/bhn-external/docs/webhooks-for-ordering-notifications

How can I retrieve eGift URLs in an eGift Fulfillment Only use case?

There are two ways to get eGift URLs:

1. Using GET API calls
Call GET /v3/orders to retrieve the eGift URL for each line item.
The eGift URL will be available for each line item once the order status is COMPLETED.

2. Using Webhook Notifications
Integrate with BHN webhooks to receive order and line item status updates
When you receive a COMPLETED order status notification, use the GET API to fetch the eGift URL
Webhooks help reduce unnecessary GET calls. For more details on webhooks see - https://developers.bhn.technology/bhn-external/docs/webhooks-for-ordering-notifications

What is scheduled delivery and how do I use it?
Scheduled delivery allows you to schedule egift delivery anywhere from a few hours to up to a year in advance. This feature is available for digital egift deliveries only. To implement scheduled delivery, include the schedule parameter in your delivery object using ISO 8601 format. The minimum scheduling time is 1 hour from the current time. Egifts are delivered at the top of the scheduled hour with a 5-minute processing buffer. Required attributes: "delivery": { "type": "DIGITAL", "email": true, // OR "text": false, "schedule": "2025-11-03T18:30:00.000Z" } Note: You must specify either email or text delivery (at least one must be true). We follow ISO 8601 standards to manage different timezones and support both date and time based scheduled delivery.

What is scheduled delivery and how do I use it?

Scheduled delivery allows you to schedule egift delivery anywhere from a few hours to up to a year in advance. This feature is available for digital egift deliveries only.
To implement scheduled delivery, include the schedule parameter in your delivery object using ISO 8601 format. The minimum scheduling time is 1 hour from the current time. Egifts are delivered at the top of the scheduled hour with a 5-minute processing buffer.
Required attributes:
"delivery": {
"type": "DIGITAL",
"email": true, // OR
"text": false,
"schedule": "2025-11-03T18:30:00.000Z"
}
Note: You must specify either email or text delivery (at least one must be true). We follow ISO 8601 standards to manage different timezones and support both date and time based scheduled delivery.