Pairly API's frequently asked questions
Welcome to the Pairly API FAQ! We recommend reading this page prior to integration. If you have any lingering questions, contact [email protected].
Can we use one Transaction ID per flight booking?
You will have to use new Transaction ID for each transaction, even if it's for the same flight booking. This query needed to fetch the most up-to-date price on carbon offsets in the inventory.
How do our customers know their purchase went through?
We will send them an email confirmation containing the receipt, information, and links.
How are refunds handled when the booking is refunded or changed?
When it comes to implementation, for a ticket exchange, a new transaction is Created and Confirmed while the old transaction is Deleted. For a refund, if you decide to refund the offsets, the original transaction is Deleted. These should be the only cases when the Delete endpoint is used.
Do you provide resources for the design of the UI?
We do have text blurbs and sample UIs in React and vanilla HTML, CSS, JS. Please reach out to [email protected] if this is of interest.
What's the difference between test and live keys?
Using test keys will not save the data into the database while using live keys will. Calling API endpoints with test keys will return the expected response, but will not send emails, charge you, or save the changes.
What currencies are supported?
We support USD, EUR, GBP, AUD, CAD, CHF, CNY, HKD, BRL. Since our system runs on top of Stripe, adding more currencies is relatively seamless.