Invoice Process Flow

Invoices are created in HTML and can be sent to the buyer directly. The API response also contains an invoice URL that you can use to integrate it into your store or applications.

An invoice is sent to the liable party, this can be either the buyer or seller. If it is the buyer, it is sent to the email specified in the buyer_email field. If this is not specified, it is sent to the seller.

The HTML version of the invoice is included in the response that is returned by the Confirm Transaction request. You can hide this URL if you prefer. See Setting Invoice URL Privacy.

Example Process Flow

The following graphic describes an example process flow showing how an invoice is sent:

The process flow is as follows. This is a simplified example and steps can vary substantially in a real implementation.

1. Buyer places goods in basket. The buyer places some goods in their basket but do not go to the checkout yet.
2. Store Transaction request is sent to Vertex for Marketplaces. The Store transaction request is sent to the service and tax information and a transaction key is returned.
3. Buyer confirms the purchase. They complete checkout.
4. Confirm Transaction request sent to Vertex for Marketplaces. The Confirm Transaction request is sent (containing the Transaction Key created in the previous step.
5. Invoice sent per settings to the buyer or merchant. An invoice is sent to the liable party, this can be either the buyer or seller. If it is the buyer, it is sent to the email specified in the buyer_email field. If this is not specified, it is sent to the merchant.
6. Buyer receives invoice.

Post Transaction Processing

Refunds and Credit Notes

See Refunds and Credit Notes.