# Loyalty Traditional Fulfillment Service source: https://developer.mastercard.com/traditional-fulfillment-service/documentation/index.md ## Overview {#overview} Loyalty Traditional Fulfillment Service is a rewards catalog and fulfillment REST API for banks, card issuers, merchants, and fintechs that run their own loyalty program. It delivers a seamless and secure way to enable a points redemption experience. A rewards program allows for the retrieval of catalogs or items based on search criteria. The fulfillment items (such as gift cards) are displayed on a consumer-facing website or used to document details in a customer-servicing application. Additionally, for the Global Rewards Platform Promotions orders that are fulfilled by external vendors the order statuses can be fetched and retrieved on the consumer-facing website. ## How It Works {#how-it-works} The Loyalty Traditional Fulfillment Service enables a redemption experience on a customer or partner-hosted experience. The retrieve catalog and retrieve items use cases document how to pull the content associated with a fulfillment item such as a short description, long description, product image, order information, and terms and conditions. Additionally, for Global Rewards Platform Promotions, the order status use case documents how to update the order status associated with a fulfilment item, for example a digital gift card. In a typical real-world scenario, a bank runs its own rewards website. A consumer signs in to spend points, the bank platform calls this service to load the reward categories and the items inside them, and the consumer redeems a gift card without leaving the bank experience. When an external vendor fulfills that order, the vendor reports the delivery status back through this service so the bank can show accurate progress. You interact with the service as a REST client. The customer platform and the external vendor both call Mastercard over HTTPS with an OAuth 1.0a signed request, the Mastercard API Gateway authenticates the caller, and the service returns catalog content, reward item detail, or a confirmed order status. For the request and response detail behind each step, see the [Use Cases](https://developer.mastercard.com/traditional-fulfillment-service/documentation/use-cases/index.md). For the signing setup, environments, and base URLs, see [API Basics](https://developer.mastercard.com/traditional-fulfillment-service/documentation/api-basics/index.md). For the full operation list, see the [API Reference](https://developer.mastercard.com/traditional-fulfillment-service/documentation/api-reference/index.md). The types of customers who will be benefiting from this service are Issuers, Merchants, and external vendors. The target groups are: * Programs where the customer is hosting the entire user experience through Mastercard Reward APIs. * Programs where Mastercard is hosting the product offering (that is, the client is using Mastercard white-labeled solutions or products) and a redemption experience is enabled on a customer or partner-hosted platform. * Programs where the external vendors are connecting to Loyalty Traditional Fulfillment Service to update the order status.
##### The following diagram shows the end-to-end integration sequence across the Consumer, Customer Platform, Mastercard API Gateway, Loyalty Traditional Fulfillment Service, and External Vendor {#the-following-diagram-shows-the-end-to-end-integration-sequence-across-the-consumer-customer-platform-mastercard-api-gateway-loyalty-traditional-fulfillment-service-and-external-vendor} Diagram how-it-works ##### The following diagram shows a high-level flow between the Consumer, Customer, and the Loyalty Traditional Fulfillment Service API for Catalogs and Items based operation {#the-following-diagram-shows-a-high-level-flow-between-the-consumer-customer-and-the-loyalty-traditional-fulfillment-service-api-for-catalogs-and-items-based-operation} ![High-level flow in which the consumer signs in to the customer application, the customer sends a signed catalog or item request to Loyalty Traditional Fulfillment Service, and the service returns the response](https://static.developer.mastercard.com/content/traditional-fulfillment-service/uploads/TFS-How-works-TP.png) ##### The following diagram shows a high-level flow between the external vendor and the Loyalty Traditional Fulfillment Service API for Orders based operation {#the-following-diagram-shows-a-high-level-flow-between-the-external-vendor-and-the-loyalty-traditional-fulfillment-service-api-for-orders-based-operation} ![High-level flow in which the external vendor sends a signed order status request to Loyalty Traditional Fulfillment Service and the service confirms the update back to the vendor](https://static.developer.mastercard.com/content/traditional-fulfillment-service/uploads/TFS-How-works-order.png) ###### Execution Steps for Catalogs and Items based operation: {#execution-steps-for-catalogs-and-items-based-operation} 1. The consumer signs into the customer's application. 2. The customer authenticates the consumer. 3. The customer sends a signed request to Loyalty Traditional Fulfillment Service. 4. The Loyalty Traditional Fulfillment Service validates the request. 5. The Loyalty Traditional Fulfillment Service will retrieve the catalog or item (which must be given a catalog). 6. The Loyalty Traditional Fulfillment Service sends the response.
###### Execution Steps for Orders based operation: {#execution-steps-for-orders-based-operation} 1. The Vendor sends a signed request to Loyalty Traditional Fulfillment Service. 2. The Loyalty Traditional Fulfillment Service validates the request. 3. The Loyalty Traditional Fulfillment Service will update the order status 4. The Loyalty Traditional Fulfillment Service sends the response. ### Good to Know {#good-to-know} * Follow the [Quick Start Guide](https://developer.mastercard.com/traditional-fulfillment-service/documentation/quick-start-guide/index.md) to make your first signed sandbox call. * We have created a [Reference Application](https://developer.mastercard.com/traditional-fulfillment-service/documentation/reference-app/index.md) to get you started. * Refer to the [Use Cases](https://developer.mastercard.com/traditional-fulfillment-service/documentation/use-cases/index.md) for additional details on how the API works. * Refer to the [Tutorials and Guides](https://developer.mastercard.com/traditional-fulfillment-service/documentation/tutorials-and-guides/index.md) for additional guidance. * See the [FAQ](https://developer.mastercard.com/traditional-fulfillment-service/documentation/faq/index.md) for common questions about catalogs, points redemption, and vendor order status. Tip: If you don't have a Mastercard representative, reach out for help from the [support page](https://developer.mastercard.com/traditional-fulfillment-service/documentation/support/index.md#get-help). ## Next Steps {#next-steps} When you are ready to use the APIs, start with the [Quick Start Guide](https://developer.mastercard.com/traditional-fulfillment-service/documentation/quick-start-guide/index.md) for an ordered path from account creation to your first sandbox call, then refer to the [API Basics](https://developer.mastercard.com/traditional-fulfillment-service/documentation/api-basics/index.md) page for API authentication, and environment details.