Charges vs transactions

The API return object for a given invoice now includes two objects: [charges] and [transactions]. I just want confirm they are what i think they are and behave the way I'd expect:

[charges] = the total amount to be charged for that invoice [transactions] = actual Auth.net transaction processes. So if the first attempt was declined but the 2nd succeeded, 2 records would show up under here.

Side question: Any way I can tell from looking at a given invoice object that the invoice is paid in full or outstanding? Is this state represented by the value of paidTransactionId?

  1. Frank -- All of those assumptions are correct. If you calculate the sum of charges (charge.quantity * charge.eachAmount) it should equal the transaction.amount.

  2. Marc Guyer closed this discussion on 25 Jan, 2010 09:02 PM.

  3. Frank Koehl re-opened this discussion on 25 Jan, 2010 09:22 PM

  4. Awesome, thanks.

    Will the total value of an invoice ever be spread across multiple transactions, or are invoice values processed atomically (i.e. all or none)?

  5. Yup, it's all or nothing.

  6. Marc Guyer closed this discussion on 25 Jan, 2010 09:51 PM.

  7. Frank Koehl re-opened this discussion on 25 Jan, 2010 09:58 PM

  8. Great, that makes my coding assumptions sooooo much easier. :)

  9. Marc Guyer closed this discussion on 25 Jan, 2010 11:07 PM.

Discussions are closed to public comments.
If you need help with Cheddar please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions