Handling e-invoicing requirements
Gain a better understanding of how to comply with e-invoicing requirements in Taiwan
Last updated
Gain a better understanding of how to comply with e-invoicing requirements in Taiwan
Last updated
If you select the option and you'd like to use the , this article outlines one possible approach you might use to handle a that is assigned a of DR_TAIWAN-ENTITY.
Before or after customers initiate checkout, use a control (such as a radio button or checkbox) to determine whether they're making the purchase as an individual or on behalf of a business. Depending on the customer's selection, display the appropriate fields in your shipping and/or billing information collection form.
If customers are making the purchase as a business entity, then your form needs to collect their organization/company name. Otherwise, that field isn't needed.
If customerType is business, then make sure you define shipTo.organization and/or billTo.organization.
If it is, determine the value of customerType.
Once you've completed either of these operations, you can collect the customer's shipping choice (when required) and payment. For details refer to:
If invoiceAttribute is populated, then you can display each of its attributes on the summary page. Similarly, if a taxIdentifiers[] exists, you can display its value on that same page.
Digital River has integrated with a third-party service that gives customers access to all of their eGUIs. As a result, you're not required to provide this information on your site. In B2C transactions, the service adds the eGUIs to a government-managed customer-accessible website. In B2B transactions, customers are sent an email that contains the eGUI number, a link to the national lottery site, and a PDF attachment of the invoice.
For each invoiceAttribute.type, the following provides an example of the data contained in order.complete.
Add a click event handler to the form's submit button that uses the data it collects to set the , and/or .
In the response, determine whether is DR_TAIWAN-ENTITY.
If customerType is individual, retrieve , use it to set sessionId in the configuration object, and then and that element. When executes, retrieve id from the event's payload and pass it as invoiceAttributeId in the body of an .
In B2C transactions, if your contains no invoiceAttributeId, then Digital River returns a 409 Conflict.
If customerType is business, retrieve payment.session.id, use it to set sessionId in the configuration object and and mount the element. Handle by checking the event's payload to determine whether elementType is taxidentifier and complete is true. If that's the case, retrieve identifier.type and identifier.value and pass them as type and value in the body of a . From the response, retrieve id and pass it as taxIdentifiers[].id in the body of an .
In B2B transactions, if your contains no taxIdentifiers[].id, then Digital River returns a 409 Conflict.
The Payment methods for Taiwan section in the
After you create the , initiate , and then receive the with a of , you could use its to build an order summary page on your site.
As part of that operation, you can determine whether the event's contains invoiceAttribute or taxIdentifiers[].
