You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In remittance use cases (perhaps trading too?), it is a pretty standard experience for Alice to get a Quote from the remittance provider in two different ways. For example, using USD > MXN currency pair, she might ask:
If I pay X USD, how much MXN will the recipient get?
If I want to send Y MXN, how much USD do I have to pay?
Currently, the RFQ allows Alice to only ask for the Quote per #1 above.
However, we should consider enabling #2 flow by adding RFQ.payout.amount field. The PFI should treat this as an XOR field so that Alice MUST send ONE of RFQ.payin.amount OR RFQ.payout.amount.
remitly_quote.mov
The text was updated successfully, but these errors were encountered:
In remittance use cases (perhaps trading too?), it is a pretty standard experience for Alice to get a Quote from the remittance provider in two different ways. For example, using USD > MXN currency pair, she might ask:
If I pay X USD, how much MXN will the recipient get?
If I want to send Y MXN, how much USD do I have to pay?
Currently, the
RFQ
allows Alice to only ask for the Quote per #1 above.However, we should consider enabling #2 flow by adding
RFQ.payout.amount
field. The PFI should treat this as an XOR field so that Alice MUST send ONE ofRFQ.payin.amount
ORRFQ.payout.amount
.remitly_quote.mov
The text was updated successfully, but these errors were encountered: