Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
merchant:existing_merchant:selfcare_system:einvoice [2018/12/03 10:26]
127.0.0.1 external edit
merchant:existing_merchant:selfcare_system:einvoice [2020/02/12 08:07]
robinc [Create an Invoice Payment Request] added Logo sizing information
Line 12: Line 12:
 </​WRAP>​ </​WRAP>​
  
-**Create eInvoice**+===== Search and Manage Invoice Payment Requests =====
  
-  * __Without a list of items__.+Each payment link generated can be found using the filter in the searchAmong those filters optios, you can use:
  
-<​html><​img ​ class="​imageReplace img_small"​ src= " +**Merchant Ref**\\ 
-data/media/merchant/existing_merchant/selfcare_system/merchant_selfcare_createpaymentlink_level2data_nu.png"​/></html> +**Customer Name**\\ 
-\\+**Customer E-mail**\\ 
 +**Status**\\ 
 + ​- ​//Open// - still not paid successfully\\ 
 + ​- ​//Complete// - successfully paid (or with a pending capture)\\ 
 + - //​Cancelled//​ - cancelled by the merchant before payment or expiration\\ 
 + - //Expired// - passed the expiration date (automatically changes to expired)\\ 
 +**Amount**\\ 
 +**Creation Date**\\ 
 +**Expiration Date**\\
  
-  ​__With ​a list of items__.+All of those options allow the user to choose among different comparators (ranges for quantities, values and dates, or matching types fo rnames and identifiers). Explore the filters and create your own searches. You can save your searches using the **SAVE** option, on the left side below the filters. 
 + 
 +Once your filters are as you need, just select the **SEARCH** option and the result is going to be paginates to your right below the search. 
 + 
 +{{:​merchant:​existing_merchant:​selfcare_system:​merchant_selfcare_paymentlink-search_nu.png |}} 
 + 
 +On the resulting list you see few fields which are useful to identify the payment link. 
 + 
 +  * **Merchant Ref** 
 +  * **Customer** 
 +  * **Creation Date** 
 +  * **Expiration Date** 
 +  * **Auth Type** 
 +  * **Status** 
 +  * **Amount** 
 + 
 +{{:​merchant:​existing_merchant:​selfcare_system:​merchant_selfcare_paymentlink-list-actions_nu.png |}} 
 + 
 +If you want more details or perform a different action over an existing payment link, at the far right column ​of the search result you can find the **ACTIONS** list for each paymnet link. Depending on the status of the payment link, different actions are possible. 
 + 
 +  * **View:** Allows the user to check details but not change them. Achieved by clicking on the **ACTION** column and selecting the **VIEW** option for a specific payment link or by clicking on the MERCHANT REF (table link) of the same payment link. Applicable for COMPLETE, CANCELLED, and EXPIRED paymnent links.\\ 
 +  * **Edit:** Allows the user to check and edit details. Achieved by clicking on the **ACTION** column and choosing the **EDIT** option for a specific payment link or by clicking on teh MERCHANT REF (table link) of the same payment link. Applicable only for OPEN payment links.\\ 
 +  * **Cancel:** Allows the user to cancel. In the **ACTION** column, choose the** CANCEL** option for a specific payment link. Applicable only for OPEN payment links.\\ 
 +  * **Send:** Allows the user to send (or resend). In the **ACTION** column, choose the **SEND** option for a specific payment link. Applicable only for OPEN payment links. 
 +  * **Copy:** Allow the user to create a new payment link from an existing one. In the **ACTION** column, choose **COPY**. Applicable for all statuses. It only opens a form copying most of the data of the selected payment link, so you can more easily create a new one from it. 
 +  * **Email Preview:** Allows the user to see how the e-mail sent by the platform is going to look like in the customer'​s email. In the **ACTION** column, choose the **EMAIL PREVIEW**. Applicable for all statuses. 
 + 
 +===== Create an Invoice Payment Request ===== 
 + 
 + 
 +To create a new payment link, you only need to provide a few details. 
 + 
 +{{:​merchant:​existing_merchant:​selfcare_system:​merchant_selfcare_paymentlink-create-noitems_nu.png |}} 
 + 
 +Depending on your needs, you might want to break down the payment in items.
  
 <​html><​img ​ class="​imageReplace img_small"​ src= " <​html><​img ​ class="​imageReplace img_small"​ src= "
Line 26: Line 68:
 \\ \\
  
-Understanding ​the fields:+Also, if your terminal does allow the use of enhanced data, you might need to provide more information. 
 + 
 +<WRAP center important 100%> 
 +The enhanced data option is only going to be presented in your screen if your terminal does allow that feature. If you are not sure about this or want to know more about the benefits of using enhanced data in your payments, contact our support team. 
 +</​WRAP>​ 
 + 
 + 
 +About the fields:
  
-  * **Logo**: Field to inform any logo the Merchant desires to used on a pay by link e-mail. +  * **Logo**: Field to inform any logo the Merchant desires to used on a invoice payment request ​e-mail
-  * **Currency**:​ Currency in which the transaction will be processed (limited to the terminal'​s currencies). +  * - __Styling: __ <img src="​{LOGOURL}"​ border="​0"​ style="​max-width:​ 200px; max-height: 70px">​ 
-  * **Order Id**: Order id to the pay by link generated (If not informed, the gateway generates ​one automatically).+  * - __Size: __ Max height: 70 px   Max width: 200px 
 +  * - __Highly Recommend: __ use a vector image to preserve scaling and resolution when resized. 
 +  * - __If the logo needs to be resized: __ maintain the aspect ratio to avoid the logo looking '​squished'​ or drawn out. 
 +  * - If the logo is larger than the max dimensions, the system will resize it.  This is why we recommend a vector image
 +  * **Currency**:​ Currency in which the transaction will be processed (limited to the terminal'​s currencies). ​It is only going to be requested if the terminal has more than one currency enabled.
   * **Merchant Ref**: Merchant reference used by the merchant to identify its payment links in its way.   * **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.   * **Expiration Date**: Date in which the payment link ceases to be valid.
Line 37: Line 90:
   * - __Name__: Name of the customer to which the payment link is addressed to.   * - __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.   * - __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. +  * **Enable Level II Data**: ​This option is going to appear only for terminals with enhanced data enabled (level II and level III). It is 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"​. +  * - __Use tax for level II data__: ​This field indicates the transaction is not exempt from tax and that the merchant wants to define ​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 shipping address__: enables the fields to provide details on the shipping address to be used at level II. It is 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. +  * **Add Items**: ​This option allows the user to define if it is 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".+  * **Items** - In this list you can ADD or REMOVE items. This option is available after the user marks **Add Items**.
   * - __Item__: Identification.   * - __Item__: Identification.
   * - __Description__:​ Short description or name.   * - __Description__:​ Short description or name.
   * - __Quantity__:​ Quantity of items.   * - __Quantity__:​ Quantity of items.
-  * - __Price__: Unitary ​prive by item.+  * - __Price__: Unitary ​price by item.
   * - __Amount__: Quantity x Price.   * - __Amount__: Quantity x Price.
   * **Transaction Details**   * **Transaction Details**
Line 54: Line 107:
 \\ \\
  
-**Send eInvoice**+===== Send an Existing Invoice Payment Request =====
  
-<​html><​img ​ class="​imageReplace img_small"​ src= " +Once created, a payment link can be sent to a customer until it is completed, cancelled, or expires. The user has two options to send the link to the customer. 
-data/media/merchant/existing_merchant/selfcare_system/​nuvei_invoice_payment_request_send.png"/></​html>​+ 
 +While creating the link (after saving as details) 
 + 
 +{{:​merchant:​existing_merchant:​selfcare_system:​merchant_selfcare_paymentlink-send-1_nu.png |}} 
 + 
 +After the link is created, at any given time (even after editing the details or changing the customer), as long as the link is not COMPLETE, EXPIRED, OR CANCELLED. 
 + 
 +{{:merchant:existing_merchant:selfcare_system:​merchant_selfcare_paymentlink-send-2_nu.png |}}
  
 Understanding the fields: Understanding the fields:
  
-  * **E-mail Preview**: Represents the body build during the eInvoice ​creationand how it is going to look like at the customer'​s e-mail box when opened.+  * **E-mail Preview**: Represents the body build during the Invoice Payment Request ​creation and how it is going to look like in 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 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.   * **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.+If the user desires, the **Pay Now Button** is a functional fragment of HTML which can be used in 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 in 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**. 
  
 \\ \\
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International