> ## Documentation Index
> Fetch the complete documentation index at: https://docs.momentco.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Providers

> Supported stored value providers and their capabilities

Providers may differ in supported capabilities, field requirements, and redemption behaviour.

The supported providers can be discovered programmatically using the [redemption types](/api-reference/collect/redemptions/get-types) endpoint. The endpoint returns each redemption `type`, its capabilities, display metadata, and required `source` attributes, allowing clients to dynamically present available providers and collect the information required to redeem them.

<Note>
  Use the discovery endpoint as the source of truth to automatically stay up to date as providers and capabilities evolve.
</Note>

## Voucher

Vouchers are redeemed through three providers today: **1Voucher**, **OTT Mobile**, and **Blu Telecom (Blu Voucher)**.

<u>Provider quick-reference</u>

| **Provider** | Type                   | Identifier                                | **Partial Redemption** | **Balance Lookup** | **Change Voucher Returned**                             | **SMS Delivery**                                           |
| :----------- | ---------------------- | ----------------------------------------- | :--------------------- | :----------------- | :------------------------------------------------------ | :--------------------------------------------------------- |
| 1Voucher     | `vouchers.one_voucher` | `pin` (16 digit)                          | Yes                    | No                 | Yes, `change_voucher` field is returned in API Response | Yes, delivered by provider when `phone_number` is supplied |
| Blu Voucher  | `vouchers.blu`         | `pin`<br />`phone_number`                 | Yes                    | Yes                | Yes, `change_voucher` field is returned in API Response | No                                                         |
| OTT Mobile   | `vouchers.ott`         | `token`<br />`serial_number` (for lookup) | Yes                    | Yes                | No                                                      | Yes, delivered by provider when `phone_number` is supplied |

**<u>1Voucher</u>**

**Redemption Behaviour**

Supports:

* Full redemption
* Partial redemption

**Remaining Value**

* Where value remains after redemption, a replacement voucher is returned through the `change_voucher` field (PIN, serial number, barcode, instructions).
* Where value remains after redemption, a replacement voucher is delivered directly to the customer by SMS using the supplied phone number.

<Note>
  The replacement PIN is the customer's only way to spend the residual balance, so it must be preserved and surfaced to the customer.
</Note>

\
**<u>Blu Voucher</u>**

**Redemption Behaviour**

Supports:

* Full redemption
* Partial redemption

**Remaining Value**

* Where value remains after redemption, a replacement voucher is returned through the `change_voucher` field.
  <Note>
    The replacement PIN is the customer's only way to spend the residual balance, so it must be preserved and surfaced to the customer.
  </Note>

**<u>OTT Mobile</u>**

**Redemption Behaviour**

Supports:

* Full redemption
* Partial redemption

**Remaining Value**

* Where value remains after redemption, a replacement voucher is delivered directly to the customer by SMS using the supplied phone number.

<Note>
  The replacement token is the customer's only way to spend the residual balance, so it must be preserved and surfaced to the customer.
</Note>

## Gift Cards

<Info>
  **Coming soon.**

  Gift cards will be supported as a stored value type in future.
</Info>

### Loyalty Points

<Info>
  **Coming soon.**

  Loyalty points will be supported as a stored value type in future.
</Info>