Where are my invoices located?


Uniregistry account holders can view their complete invoice and transaction history within their Uniregistry account manager.


Steps to locate your Uniregistry invoices


1.  Log in to your account at Uniregistry.com by clicking the ‘Log In/Sign Up’ button in the upper-right corner of the homepage.





2.  Click on the arrow next to ‘Account’ and select ‘Order History’ from the drop-down menu.






3.  From here, you can view invoices for all past transactions.

Filter the number of entries per page by clicking the ‘Per Page’ drop-down menu and use the arrows to scroll through pages.





4.  Click on a row to open and review that invoice.  Use the ‘Print’ and ‘Email’ buttons to save a pdf or resend the invoice to the account email address.


Order History - Invoice view

Was this article helpful?
2 out of 2 found this helpful


  • Uniregistry Domain ManagementDomain Renewals

    How do I enable or disable auto renew for a domain name?


    January 20, 2017 07:16


    We don’t want you to lose your names due to missed renewal notices, that’s why there’s auto-renew. When enabled, it automatically charges your default payment profile approximately 30 days before the domain expires so you don’t have to worry. Notices are sent 7-10 days before the pending charge date to let you know which domains are being renewed. Want to make a change or cancel? No problem, simply log into your account and disable auto-renew for the domains you don’t want to be renewed.                                       

    *Auto-renewals are refundable within 5-days from the transaction per registry standards. 


    Steps to enable or disable auto-renew for your domains


    1.  Log in to your account at Uniregistry.com by clicking the ‘Log In/Sign Up’ button in the upper-right corner of the homepage.





    2.  Click ‘Manage’ from the menu at the top of the page.






    3.  Click on the green circling arrows icon located to the far right of the domain and wait a few moments for it to turn into a gray arrow.



    To disable auto-renew for several domains, simply select the ones you want (or paste a list in the search bar) and click one of the the green arrows icons in the list.

    To disable auto-renew for all of your domains click the small arrow next to the checkbox in the header bar and select ‘All # domains’.

    To enable auto-renew simply click the gray arrow icon and wait for it to turn into green circling arrows.


    Was this article helpful?


    0 out of 0 found this helpful

    Facebook Twitter LinkedIn


    1 comment

    Sort by

    mark vines

    January 21, 2019 08:14

    wot go on dude


    Please sign in to leave a comment.

    Recently viewed articlesWho can register a .KY domain name?How do I renew a domain name at Uniregistry?What is Privacy.Link™?

    Related articlesHow do I delete a domain name at Uniregistry?How do I create a new payment profile?What bulk edit functions are available?How do I change my Uniregistry account password?How to checkout using Uniregistry's Secure Exchange (SE)

    © Uniregistry


    Domain Management

    ProductsWhat is Documents.Link™ ?What is the Uniregistry Domain Tracker?Domain PushesCan I push domain names to another Uniregistry account in bulk?How do I transfer a domain name between Uniregistry accounts?How do I push a domain name to another account?Domain Transfer In How do I transfer domain names to Uniregistry?How do I resend a Form of Authorization (FOA)?Why haven’t I received an FOA for my transfer request?Domain Transfer OutHow do I transfer a domain name away from Uniregistry?How to expedite a transfer away from UniregistryWhy can’t I transfer a new domain name to another registrar?How am I notified to approve a domain name transfer request?Where is my domain name authorization (EPP) code?What is the Uniregistry Resolution Center?General FAQs What is a WHOIS lookup?How to submit an abuse report to UniregistryHow do I configure my domain for Sqaurespace?How do I change ownership for my .com.au domain?What is the Uniregistry Resolution Center?Does Uniregistry accept domain name pre-registrations?See all 20 articlesRegistrationWho can register a .co.uk domain name?How do I register a new domain name at Uniregistry?Domain DNSHow do I configure my domain for Tumblr?What bulk edit functions are available?How do I forward my domain with a mask?How do I forward a domain name to a Facebook page?How do I forward a domain name to a LinkedIn profile?How do I manage A records?See all 12 articlesSecurityHow do I lock a domain name?How do I enable Privacy.Link™?How do I get the authorization (EPP) code for a domain name?How do I unlock a domain name?What does ‘Client Transfer Prohibited’ mean?Domain RenewalsHow do I renew domain names in bulk?Can I register/renew a domain name for more than 10 years?How do I renew/restore my domain after it’s expired?Does Uniregistry have an affiliate program?How do I renew a domain name at Uniregistry?How do I enable or disable auto renew for a domain name?See all 7 articlesName ServersHow do I accept a domain push?How do I assign Uniregistry’s default name servers to a domain name?How do I assign custom name servers to my domain?How do I update my name server records?

    © Uniregistry



    Sign In

    Developer terms

    More about restricted uses of the Twitter APIs.

    Use of our developer platform requires that you review and agree to ourDeveloper Agreement and Policy, as well as our related policies, including the Display Requirements andAutomation Rules. Among other things, our agreements and policies provide guidance about several restricted use cases. We’ve provided additional information about some of these restrictions below.

    Sensitive information

    You should be careful about using Twitter data to derive or infer potentially sensitive characteristics about Twitter users. Never derive or infer, or store derived or inferred, information about a Twitter user’s:

    Health (including pregnancy)Negative financial status or conditionPolitical affiliation or beliefsRacial or ethnic originReligious or philosophical affiliation or beliefsSex life or sexual orientationTrade union membershipAlleged or actual commission of a crime


    Aggregate analysis of Twitter content that does not store any personal data (for example, user IDs, usernames, and other identifiers) is permitted, provided that the analysis also complies with applicable laws and all parts of the Developer Agreement and Policy.

    Off-Twitter matching

    Off-Twitter matching involves associating Twitter content, including a Twitter username or user ID, with a person, household, device, browser, or other off-Twitter identifier. One example would be associating a Twitter username with a business’s customer records (i.e. “John Doe” in your customer record is matched to @johndoe on Twitter).

    We want people to feel comfortable to create a separate and, if they choose, pseudonymous identity on Twitter. If you intend to associate any information about a Twitter user with an off-Twitter identifier, we require that you get express, opt-in consent from the user before making the association. For example, you could get this consent if the user shares their Twitter handle directly with you as part of a signup process for your service.

    In situations in which you do not have a user’s express, opt-in consent to link their Twitter identity to an off-Twitter identifier, we require that any connection you draw be based only on information that a user would reasonably expect to be used for that purpose. If a user would be surprised to learn that you are using information they provided to link their Twitter account to an identity off of Twitter, don’t do it. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a Twitter identity based on:

    Information provided directly to you by the user. Records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or
    Public data. “Public data” in this context refers to:Information about a user which you obtained from a public, generally-available resource (such as a directory of members of a professional association)Information on Twitter about a user which is publicly available, including:TweetsProfile information, including a user’s bio and publicly-stated locationDisplay name and username


    Redistribution of Twitter content

    If you need to share Twitter content you obtained via the Twitter APIs with another party, the best way to do so is by sharing Tweet IDs, Direct Message IDs, and/or User IDs, which the end user of the content can then rehydrate (i.e. request the full Tweet, user, or Direct Message content) using the Twitter APIs. This helps ensure that end users of Twitter content always get the most current information directly from us.

    We permit limited redistribution of hydrated Twitter content via non-automated means. If you choose to share hydrated Twitter content with another party in this way, you may only share up to 50,000 hydrated public Tweet Objects and/or User Objects per recipient, per day, and should not make this data publicly available (for example, as an attachment to a blog post or in a public Github repository).

    There are a few other points to keep in mind about redistributing Twitter content:

    You may only distribute up to a total of 1,500,000 Tweet IDs to a single entity within a 30 day period unless you’ve received prior express written permission from Twitter.
    Individuals redistributing Tweet IDs and/or User IDs on behalf of an academic institution for the sole purpose of non-commercial research are permitted to redistribute an unlimited number of Tweet IDs and/or User IDs.
    To request permission to share Twitter content as outlined above, please use the API Policy support form.


    To the extent you are permitted to distribute Twitter content to a third party, note that this content remains subject to the Developer Agreement and Policy, and you must ensure such third party has agreed to the Twitter Terms of Service, Privacy Policy, Developer Agreement, and Developer Policy before receiving Twitter content.

    Multiple applications

    You are not permitted to register multiple applications for a single use case, or substantially similar or overlapping use cases. Learn more about these policies here.

    In this context, we define “use case” as a consistent set of analyses, displays, or actions performed via an application. Providing the same service or application to different end users (including “white label” versions of a tool or service) counts as a single use case. These rules apply both to applications you register, and to applications registered by the end users of your tool or service; requiring your end users to register applications for the purpose of using your tool or service could result in enforcement actions against you, your applications, your customers, and/or the end users of your tool or service.

    The only exception to this rule is to create development (“dev”), staging, and production (“prod”) instances of the same service. Ensure that these applications are clearly labeled (for instance, in the application name or description), and that you do not use development or staging applications for production purposes.

    Automation, spam, and auto-responses

    The use of Twitter’s APIs and developer products to create spam, or engage in spammy behavior, is prohibited. You should review the Twitter Rules on spam, and ensure that your application does not, and does not enable users to, violate our policies.

    If your application will be used to perform write actions on the Twitter service, including posting Tweets, following accounts, or sending Direct Messages, you should carefully review the Automation Rules to ensure your service complies with our guidelines. In particular, you should:

    Always get a user’s explicit consent before sending them automated replies or messagesImmediately respect user requests to opt-out of being contacted by youNever perform bulk, aggressive, or spammy actions, including bulk followingNever post identical or substantially similar content across multiple accounts


    Measuring the Twitter service

    Do not use the Twitter APIs to measure the availability, performance, functionality, or usage of Twitter for benchmarking or competitive purposes. For example, you should never use the Twitter APIs to:

    Calculate aggregate Twitter user metrics, such as the total number of active users or accountsCalculate aggregate Twitter Tweet metrics, such as the total number of Tweets posted per day, or the number of user engagements or account engagementsMeasure or analyze spam or security on Twitter, except as permitted in the Twitter Rules


    Surveillance, privacy, and user protection

    At Twitter, protecting and defending the privacy of our users is built into the core DNA of our company — and our developer and data products reflect that commitment. We believe that Twitter data can be a powerful force for good in the world — from saving lives during flooding in Jakarta to helping the USGS track earthquakes to working with the UN to achieve the Sustainable Development Goals. However, we prohibit the use of Twitter data and the Twitter APIs by any entity for surveillance purposes, or in any other way that would be inconsistent with our users' reasonable expectations of privacy. Period.

    We describe prohibited uses of our data and developer products in the Developer Agreement, including prohibitions on investigating or tracking Twitter users or their content, as well as tracking, alerting, or monitoring sensitive events (such as protests, rallies, or community organizing meetings).

    Other categories of activities prohibited under these terms include (but are not limited to):

    Investigating or tracking sensitive groups and organizations, such as unions or activist groupsBackground checks or any form of extreme vettingCredit or insurance risk analysesIndividual profiling or psychographic segmentationFacial recognition


    These policies apply to all users of our APIs. Any misuse of the Twitter APIs for these purposes will be subject to enforcement action, which can include suspension and termination of access.

    For additional information for law enforcement authorities seeking information about Twitter accounts, visit https://t.co/le.

    Developer policy and terms

    Follow @twitterdev

    Subscribe to developer news



    Comment actions Permalink
  • Lilenemy_

    Comment actions Permalink

    Comment actions Permalink

Please sign in to leave a comment.