This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
merchant:existing_merchant:selfcare_system:einvoice [2018/11/12 12:08] thiago123 Updated for release of version 5.6 |
merchant:existing_merchant:selfcare_system:einvoice [2018/12/03 10:26] 127.0.0.1 external edit |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== eInvoice ====== | ||
+ | |||
+ | ~~TOC~~ | ||
+ | |||
+ | \\ | ||
+ | The **eInvoice** provides merchants with the ability to create and send links to request payments from customers. The merchant pre-configures a payment informing the basic details and the elements that should appear on the customer's notification, identifies the customer and then the merchant can send an e-mail using the SelfCare system, or manually by its own means. | ||
+ | |||
+ | <WRAP important 100%> | ||
+ | |||
+ | The Merchant needs to have a terminal configured to work with Hosted Payment Pages. Only terminals with this configuration enabled will allow the use of the eInvoice feature. | ||
+ | |||
+ | </WRAP> | ||
+ | |||
+ | **Create eInvoice** | ||
+ | |||
+ | * __Without a list of items__. | ||
+ | |||
+ | <html><img class="imageReplace img_small" src= " | ||
+ | data/media/merchant/existing_merchant/selfcare_system/merchant_selfcare_createpaymentlink_level2data_nu.png"/></html> | ||
+ | \\ | ||
+ | |||
+ | * __With a list of items__. | ||
+ | |||
+ | <html><img class="imageReplace img_small" src= " | ||
+ | data/media/merchant/existing_merchant/selfcare_system/merchant_selfcare_createpaymentlinkitems-nu.png"/></html> | ||
+ | \\ | ||
+ | |||
+ | Understanding the fields: | ||
+ | |||
+ | * **Logo**: Field to inform any logo the Merchant desires to used on a pay by link e-mail. | ||
+ | * **Currency**: Currency in which the transaction will be processed (limited to the terminal's currencies). | ||
+ | * **Order Id**: Order id to the pay by link generated (If not informed, the gateway generates one automatically). | ||
+ | * **Merchant Ref**: Merchant reference used by the merchant to identify its payment links in its way. | ||
+ | * **Expiration Date**: Date in which the payment link ceases to be valid. | ||
+ | * **Description**: Description to inform what the payment link created is related to. Useful specially in cases where the merchant needs to provide context beyond the items for a payment link. | ||
+ | * **Customer Information** | ||
+ | * - __Name__: Name of the customer to which the payment link is addressed to. | ||
+ | * - __Email__: E-mail of the customer in which the payment link should be receive. | ||
+ | * **Enable Level II Data**: this option is going to appear only for terminals with enhanced data enabled (level II and level III). It's going to allow the user to define level II data for a customer. The shipping address details, if informed, will be editable at the Hosted Payment Page, so the customer can change, but the tax information is mandatory. | ||
+ | * - __Use tax for level II data__: this field indicates that the transaction is not exempt from tax and that the merchant wants todefine a value, even if it's "0". | ||
+ | * - __Add shipping address__: enables the fields to infor the shipping address to be used at level II. It's going to be editable by the customer when in the Hosted Payment Page. | ||
+ | * **Add Items**: this option allows the user to define if it's necessary to add a list of items to the payment link or if not. | ||
+ | * **Items** - In this list you can ADD or REMOVE items. This option is available after the user marks "Add Items". | ||
+ | * - __Item__: Identification. | ||
+ | * - __Description__: Short description or name. | ||
+ | * - __Quantity__: Quantity of items. | ||
+ | * - __Price__: Unitary prive by item. | ||
+ | * - __Amount__: Quantity x Price. | ||
+ | * **Transaction Details** | ||
+ | * - __Subtotal__: SUM of all Items (Quantity x Price). | ||
+ | * - __Tax(%)__: Additional taxes the merchant might want or need to apply to a transaction. | ||
+ | * - __Total__: Subtotal + (Subtotal*Tax) | ||
+ | * **Footer Notes**: This area serves the purpose of additional descriptions, information or disclaimers. | ||
+ | \\ | ||
+ | |||
+ | **Send eInvoice** | ||
+ | |||
+ | <html><img class="imageReplace img_small" src= " | ||
+ | data/media/merchant/existing_merchant/selfcare_system/nuvei_invoice_payment_request_send.png"/></html> | ||
+ | |||
+ | Understanding the fields: | ||
+ | |||
+ | * **E-mail Preview**: Represents the body build during the eInvoice creation, and how it is going to look like at the customer's e-mail box when opened. | ||
+ | * **Pay Now Button**: A fragment of HTML code already configured to redirect the customer to the merchant's hosted payment page. | ||
+ | * **Pay Now URL**: Also configured to redirect the customer to the merchant's hosted payment page, but just the URL, without the styling to look like a button. | ||
+ | |||
+ | If the user desires, the **Pay Now Button** is a functional fragment of HTML which can be used to any e-mail body to generate a button to redirect to the final payment page for the customer. Also, the **Pay Now URL** can be used for the same situation. | ||
+ | |||
+ | In case the user does not desire or can't provide by itself the e-mail, the SEND button can be used to send the e-mail, as presented on the **E-mail Preview**. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | |||