Payment Processors and Payment Methods
A payment processor is the service that actually takes the money; a payment method is what the customer chooses to pay with. Each processor supports its own set of methods.
New integrations use PAR Pay. It is the payment processor for PAR Ordering, and it is what you should expect to be configured for your brand:
| ID | Processor | Use |
|---|---|---|
| 38 | PAR Pay | Cards, Apple Pay, Google Pay and gift cards on one processor, for web and mobile ordering. What new brands report |
| 32 | Aurus | The earlier PAR Pay integration for cards and wallets. Brands onboarded before PAR Pay 38 still report it |
| 35 | Aurus Gift Card | Gift cards on those earlier brands, configured alongside 32 |
| 36 | Aurus F2F | Face-to-face terminal payments, used by on-premise devices such as kiosks |
The PAR Pay guide covers how to implement both. Build for 38 and read payment_processor_type_id from every payment initialization: a brand onboarded earlier answers with 32 and 35, and the card form and wallet payloads are shaped differently there.
Do not hard-code any of this. Which processors and methods a customer can use depends on the brand, the venue and the order type, and the combination is returned to you at runtime. Call Init application and read payment_processors and available_payment_methods, then use the UUIDs from that response when you initialize a payment.
Cash and house account
Besides the PAR Pay and Aurus processors above, two more IDs can appear on a payment, depending on how the brand is configured:
| ID | Payment Processor |
|---|---|
| 19 | Cash |
| 37 | House Account |
Cash is paid at the venue. A house account is a credit line the brand extends to an organization; see Request House Account. Neither needs a payment session: initialize the payment, get additional_info: null and no actions, and create the order.
Other IDs exist for processors from earlier markets. They are not offered to new integrations and are not documented here. If a payment initialization returns one, you cannot complete that payment: show the customer a generic payment error. If a historical receipt carries one, the payment already happened; keep the receipt's status as returned and show a generic processor label instead of the name.
Payment Methods
| ID | Payment Method |
|---|---|
| 1 | Credit Card |
| 7 | Cash |
| 10 | ApplePay |
| 12 | GooglePay |
| 14 | GiftCard |
| 20 | Pay-By-Link |
| 21 | House Account |
Note that the API returns these names without spaces where the table shows them that way — ApplePay, GooglePay and GiftCard are single words in responses.
Pay-By-Link is for catering orders the brand takes over the phone: no card is collected in the ordering app, the customer pays later through a payment link the brand sends them. It runs on the venue's Aurus processor and is accepted only when brand staff place a catering order on the customer's behalf through the call center; a payment initialization with it from a regular customer session is rejected. You will see it on receipts of such orders, not as a method to offer in your checkout.
