Credit Cards
Overview
Juno supports paying for guest travel and expenses with your organization’s existing credit cards in addition to (or instead of) the Juno Spend Account. Each credit card you add becomes a payment method that can be referenced by your Payment Method Selection rules, so you can route spend to the right card based on department, cost center, trip purpose, or any custom condition.
Credit cards live alongside other payment methods in the dashboard. Coordinators can also add their own personal credit cards from the same surface; see Managing Payment Methods for the coordinator workflow.
Card Types
When you add a credit card, you choose between two types:
- Organization Card: Visible to all administrators and available for use in payment selection rules. Use this for cards owned by your organization that should pay for guest spend across many invitations.
- Individual Card: Only visible to the person who added it. Use this when a coordinator needs to pay for a specific guest’s travel out of their own pocket. Individual cards are not selectable in organization-wide payment rules. The Credit Cards filter chip refers to these as “Personal” cards.
This page covers organization cards. Coordinators who need to add a personal card for a specific guest should follow Managing Payment Methods.
Adding an Organization Credit Card
Navigate to Credit Cards
From the admin dashboard, go to Payments → Credit Cards.
Open the Add Credit Card Drawer
Click Add Credit Card at the top of the page.
Enter Card Details
Provide the card number, expiration date, security code, cardholder name, and billing address. Card details are tokenized immediately and only the last four digits and expiration date are visible after saving.
Choose Organization
When prompted for card type, select Organization Card. The card will be saved to your organization and made available to payment selection rules.
After the card is saved, it appears in the Credit Cards list. Click into the card to configure how it should be used for each spend category.
How a Credit Card Is Used Per Category
Each organization credit card has independent settings for how Juno should handle charges in each spend category. Open the card and go to the Settings tab to configure the following:
| Category | Options |
|---|---|
| Flights | Transmit card details to airline · Charge card with Juno as merchant |
| Hotels | Transmit card details to hotel · Charge card with Juno as merchant |
| Ubers | Charge card with Juno as merchant (required) |
| Expenses | Charge card with Juno as merchant (required) |
Transmit Card Details to Vendor
Juno securely transmits the card details directly to the airline or hotel. The vendor charges the card and is the merchant of record for the transaction. There is no additional Juno processing fee on transactions handled this way.
When card details are transmitted to a hotel, Juno cannot complete credit card authorization forms on the guest’s behalf — we do not have access to the full card number. Coordinators receive instructions for completing the authorization form manually with the hotel.
Charge Card with Juno as Merchant
Juno charges your credit card directly and pays the airline, hotel, Uber, or expense recipient on your behalf. Juno is the merchant of record for the transaction. A processing fee applies to recover card-network costs.
This option is required for Ubers and Expenses: Uber’s voucher program and out-of-pocket expense reimbursements both require Juno to handle the charge so that the card can be applied across many small transactions and refunds.
On your card statement, charges that collect guest expense reimbursements appear as JUNO* REIMBURSE, and Uber rides appear as JUNO* UBER FARE or JUNO* UBER TIP.
For Hotels, choosing “Charge card with Juno as merchant” lets Juno fill in CC authorization forms on the guest’s behalf, removing the manual coordinator step described above.
Cardholder Information
Some cards require additional cardholder verification for use with certain vendors. Open the card and go to Cardholder to upload identification documents and provide the cardholder’s address. Cardholder details are stored securely and used only for verification — they are not visible after upload.
Per-Card Transactions and Receipts
Each credit card has its own transaction history and reconciliation view, separate from the Juno Spend Account.
Transactions Tab
The Transactions tab on a credit card shows every charge and refund processed through that card, including:
- Bookings (flights, hotels, Ubers)
- Payouts to guests for approved expenses
- Refunds for cancellations or changes
Each row links to the booking, guest, or expense it relates to, and includes the custom field values configured on your organization (for example, department or cost center) so you can match transactions to your accounting system.
You can export transactions as CSV from this tab for use in journal entries.
The Approval Notes column includes internal notes from the linked booking or expense’s latest request only when that request is approved, either manually or automatically. The column stays blank if there are no notes or the latest request is pending, denied, or canceled. Guest-facing reasons are not used in place of internal notes.
Refunds of Juno-collected charges
When a charge Juno made as merchant to collect a reimbursement payout or an Uber fare or tip is refunded to the card, the refund appears as its own credit row, labeled Reimbursement payout refund, Uber fare refund, or Uber tip refund. A refund of a reimbursement payout charge shows as one row for the refunded total, not one row per expense on the payout. The same rows appear in the CSV export.
If a refund later fails (for example, because the card was closed), an offsetting charge row labeled … refund failed is added. It cancels the earlier refund credit — it isn’t a new purchase.
Returned reimbursement payouts
Sometimes a reimbursement Juno sends to a guest comes back — for example, because the guest’s bank rejected the transfer. If Juno had already collected that reimbursement payout from your card, Juno refunds the charge in full, including the processing fee, to the card it was charged to. The refund appears as a Reimbursement payout refund row.
Juno doesn’t collect a replacement payout for the same expenses until that refund has gone through. If the refund fails, or part of the charge was already refunded some other way, Juno support follows up before anything is collected again. This applies to reimbursements collected as one payout charge. Expenses charged at approval are handled separately.
Receipts
When Juno is the merchant of record for a transaction (the Charge card with Juno as merchant option), Juno generates a receipt that is available for download from the transaction detail. Receipts are useful for cards where the issuer requires itemized documentation for travel and expense purchases.
When card details are transmitted to a vendor, the vendor issues the receipt directly — Juno does not generate one in this case.
To download a Juno-generated card receipt, you need permission to manage payments or to invite travelers, in the organization that owns the charge. Being a member of the organization, or the guest whose trip was charged, isn’t enough. Expense receipts that guests upload are separate and aren’t affected by this.
Hotel Folio Email
For hotel stays, you can configure an email address that should receive folios from hotel partners. Open the card and go to Settings → Hotel Folio Email. When set, Juno requests that hotels send post-stay folios (the itemized receipt for room charges, taxes, and incidentals) to this address, helping you reconcile hotel charges that vary from the original quote.
Removing a Credit Card
Delete a credit card from the Credit Cards page or from the card’s detail view. Before removing a card, confirm it is not currently referenced by any payment selection rule — if it is, update the rule first or invitations relying on that rule will fall back to the default payment method.
Removing a card does not cancel bookings already paid for with it. Refunds and post-booking adjustments for past transactions continue to flow through the original card unless it has been deactivated by the issuer.
Related Documentation
- Payment Method Selection — Use credit cards in conditional payment rules
- Juno Spend Account — How JSA-based payments work alongside credit cards
- Managing Payment Methods (Coordinators) — Coordinator workflow for individual cards