Well....
As much as i'd like to say you shouldn't worry, i'd be lying...
IF the sender is an honest person, chances of things ending badly are small tough, and a swift reply to a support ticket is usually a good sign.
Basically: your unconfirmed transaction (and it's unconfirmed parents) are now sitting in the mempools of many nodes. However, the default node setting is to remove unconfirmed transactions from it's mempool after 3 days. If most of the network's nodes forgot about your transaction, the network will act like it never existed in the first place... If your transaction isn't in most of the mining nodes mempools anymore, chances of it confirming will drastically reduce (eventually to 0% chance).
This isn't a complete disaster... If you save the raw transactions, you can always rebroadcast them (if the sender is an honest person or company, they might even rebroadcast unconfirmed transactions themselfs).
The bigger problem lies in the fact that as long as the unconfirmed transaction chain doesn't end up in a block, there is always a possibility the sender re-uses the unspent output he used as an input for your transaction in a transaction with a higher fee. If he agressively broadcasts this second transaction, and it ends up in a block, your transaction will be "cancelled"... It becomes invalid the second the double spending transaction ends up in a block.
But, like racquemis already said: the fee is high(ish) enough for your transaction to end up in a block sooner or later, and if the sender is an honest company, chances of things going sour are slim... I'd still save the raw transactions from the chain tough, just in case i'd need to rebroadcast them. In order to do this, look up the transactions on my site: https://www.mocacinno.com/page/getraw