Zuora Connector Technical Specifications
Objects Fusion Reads:
|Zuora Object||Fusion Object|
account-codes: An array of all the accounting codes in your chart of accounts. Each accounting code has fields like name, id, type (AccountsReceivable, CashOther, Assets, Customer, CashOnAccount, etc.), status, types, and more.
payment-methods: The Payment Methods resource group provides REST methods to access your customers' credit card payment methods (defaultPaymentMethod, cardType, cardNumber, and more).
debitmemos: Debit memos increase the amount a customer owes. It is a separate document from the invoice. Debit memos can be used to correct undercharging on an invoice or to levy ad hoc charges outside the context of a subscription. Just like an invoice, debit memo balances can be settled by applying either a payment or a credit memo.
creditmemos: Credit memos reduce invoice and account balances. By applying one or more credit memos to invoices with positive balances, you can reduce the invoice balances in the same way that applying a payment to an invoice. Like invoices, debit and credit memos are legal documents vendors issue to their customers. They are used to correct charge mistakes on invoices and to manage the balance due on a particular invoice or account.
paymentgateways: A payment gateway is an online service provider that connects an electronic shopping cart or virtual terminal/POS to an electronic payment processor. It is your gateway to the rest of the payments infrastructure that allows you to accept electronic forms of payment. The main function of a gateway is to pass authorization, payments, and settlement data securely to and from the merchant's website to the merchant's processor. The merchant processor in turn connects to the card association (or "network"), which connects to the card issuing bank.
For more information, visit Zuora's API documentation here.
- Call limit: 40 concurrent requests
More on the technical limits for Zuora can be found here.