FX Double Touch Option
Table of Contents
An FX double touch option is the touch product with two levels. It
pays a fixed amount depending on whether a rate touches either level.
ORE models it with the trade type FxDoubleTouchOption. This note
records the domain grounding, as ORE documents it in its product
catalogue.
1. Identifiers
What a trader books it as, and what to grep for. The codes are the trade type catalogue's, which is what the database enforces.
| Field | Value |
|---|---|
| Full name | FX Double Touch Option |
| Short name | FX Double Touch Option |
| ORE Studio product code | FxDoubleTouchOption |
| Asset class | fx |
| Family | Option |
| ORE trade data node | FxDoubleTouchOptionData |
| ORE documentation | fx_doubletouchoption.tex |
2. Summary
An FX double touch option combines two continuously monitored barriers with a cash-or-nothing digital underlying. It pays a fixed amount or zero, depending on whether the spot rate reaches one of the levels. A knock-in, or double one-touch, pays if a barrier is breached. A knock-out, or double no-touch, pays if neither is breached. Payout at expiry is the only supported mode. No rebates are supported.
3. Detail
3.1. What it is
ORE defines the product as follows:
This product has two continuously monitored barriers with a Cash-or-Nothing digital underlying.
Source: ORE User Guide, Products catalogue, fx_doubletouchoption.tex.
ORE states the payoff condition as follows:
A FX Double Touch option pays either a fixed predetermined payoff amount or zero (Cash-or-Nothing) depending upon an FX spot rate reaching one of the pre-set barrier levels.
Source: ORE User Guide, Products catalogue, fx_doubletouchoption.tex.
ORE also states the two forms. A knock-in, or double one-touch, has a fixed payout if one of the barriers is breached, and no payout otherwise. A knock-out, or double no-touch, has no payout if one of the barriers is breached, and a fixed payout otherwise. The buyer pays a premium to the seller.
3.2. In plain terms
An FX double touch option is a bet on a corridor. One side bets that the rate touches either wall before expiry. The other side bets that it never does. The payout is fixed. There is no middle ground.
3.3. How it works in ORE
The FxDoubleTouchOptionData node includes one OptionData node and
one BarrierData node. The barrier Type is KnockOut or
KnockIn. Levels holds the two levels. The OptionType can be
omitted. PayOffAtExpiry selects the payout timing. Only payout at
expiry is currently supported, for both knock-out and knock-in
barriers. PayoffAmount and PayoffCurrency set the fixed payout.
ForeignCurrency and DomesticCurrency name the rate.
StartDate sets the monitoring start, with the Calendar and
FXIndex naming the fixing source.
ORE notes that the current implementation supports FX double touch options with payout at expiry only. No rebates are supported.
3.4. Mathematical notes
The value is the probability of the touch condition, discounted, times the fixed payout. A knock-in pays when the rate breaches either level at any time before expiry. A knock-out pays when it breaches neither. The probability of touching either level rises with volatility and with time. With payout at expiry, the timing of the touch does not change the payout date.
3.5. What moves its value (static sensitivities)
- The FX spot rate. Its position inside the corridor sets the state.
- The volatility of the pair. It drives the touch probability.
- The interest rates in the two currencies.
- The two barrier levels and the fixed payout.
- The payoff currency and the fixing source.
A double no-touch loses value as spot approaches either level. A double one-touch gains. Near the levels the delta and vega change direction.
3.6. How the profile ages (dynamic sensitivities)
The two levels are monitored continuously. A one-touch can be decided at any moment, though the payout waits for expiry. A no-touch stays alive while spot stays inside the corridor. As expiry approaches, the remaining time to touch shrinks. At expiry the payout settles and the trade stops.
3.7. Why a customer would want it
A customer who expects the rate to stay in a range sells a double no-touch and collects the premium. A customer who expects a breakout buys a double one-touch. In ORE Studio a customer books FX double touch options to value them and run sensitivities on the ORE engine.
3.8. Example
ORE's catalogue shows a long double no-touch:
<FxDoubleTouchOptionData> <OptionData> <LongShort>Long</LongShort> <PayOffAtExpiry>true</PayOffAtExpiry> <ExerciseDates> <ExerciseDate>2021-12-14</ExerciseDate> </ExerciseDates> ... </OptionData> <BarrierData> <Type>KnockOut</Type> <Levels> <Level>1.1</Level> <Level>1.2</Level> </Levels> </BarrierData> <ForeignCurrency>EUR</ForeignCurrency> <DomesticCurrency>USD</DomesticCurrency> <PayoffCurrency>USD</PayoffCurrency> <PayoffAmount>100000</PayoffAmount> <StartDate>2019-01-25</StartDate> <FXIndex>FX-ECB-EUR-USD</FXIndex> <Calendar>TARGET</Calendar> </FxDoubleTouchOptionData>
Source: ORE User Guide, Products catalogue, fx_doubletouchoption.tex,
listing FX Double Touch Option data (optional elements omitted).
The single-level form is the FX Touch Option.
4. See also
- Knowledge — the hub of all knowledge notes, with the alphabetical product run.
- Wikipedia: Binary option. This places the fixed payout concept.
- Wikipedia: Barrier option. This places the barrier condition.
- ORE User Guide, Product catalogue: products.tex, which inputs fx_doubletouchoption.tex. The upstream project is OpenSourceRisk/Engine.