XML 26 R11.htm IDEA: XBRL DOCUMENT
v3.8.0.1

REVENUES | 3 Months Ended
--- | ---
Mar. 31, 2018
Revenue from Contract with Customer [Abstract] |
REVENUES | REVENUES We are a leading worldwide provider of payment technology and software solutions delivering innovative services to our customers globally. Our technologies, services and employee expertise enable us to provide a broad range of solutions that allow our customers to accept various payment types and operate their businesses more efficiently. We distribute our services across a variety of channels to customers. The following disclosures in this note are applicable for the three months ended March 31, 2018. The following table presents a disaggregation of our revenue from contracts with customers by distribution channel for the three months ended March 31, 2018:
| North America |  | Europe |  | Asia-Pacific |  | Total
| (in thousands)
Direct distribution: |  |  |  |  |  |  |
Relationship-led | $ | 226,420 |  |  | $ | 92,214 |  |  | $ | 35,242 |  |  | $ | 353,876 |
Technology-enabled | 283,358 |  |  | 51,063 |  |  | 22,429 |  |  | 356,850 |
| 509,778 |  |  | 143,277 |  |  | 57,671 |  |  | 710,726 |
Wholesale | 84,251 |  |  | — |  |  | — |  |  | 84,251 |
| $ | 594,029 |  |  | $ | 143,277 |  |  | $ | 57,671 |  |  | $ | 794,977 |
ASC 606 requires that we determine for each customer arrangement whether revenue should be recognized at a point in time or over time. For the three months ended March 31, 2018, substantially all of our revenues were recognized over time. Nature of our Customer Arrangements Our payment services customers contract with us for payment services, which we provide in exchange for consideration for completed transactions. Our payment solutions are similar around the world in that we enable our customers to accept card, electronic and digital-based payments at the point of sale. Our comprehensive service includes authorization services (including electronic draft capture), settlement and funding services, customer support and help-desk functions, chargeback resolution, payment security services, consolidated billing and statements and on-line reporting. In addition, we may sell or rent point-of-sale terminals or other equipment to customers. At contract inception, we assess the goods and services promised in our contracts with customers and identify a performance obligation for each promise to transfer to the customer a good or service that is distinct. For our payment services specifically, the nature of our promise to the customer is that we stand ready to process transactions the customer requests on a daily basis over the contract term. Since the timing and quantity of transactions to be processed by us is not determinable, we view payment services to comprise an obligation to stand ready to process as many transactions as the customer requires. Under a stand-ready obligation, the evaluation of the nature of our performance obligation is focused on each time increment rather than the underlying activities. Therefore, we view payment services to comprise a series of distinct days of service that are substantially the same and have the same pattern of transfer to the customer. Accordingly, the promise to stand ready is accounted for as a single-series performance obligation. In order to provide our payment services, we route and clear each transaction through the applicable payment network. We obtain authorization for the transaction and request funds settlement from the card issuing financial institution through the payment network. When third parties are involved in the transfer of goods or services to our customer, we consider the nature of each specific promised good or service and apply judgment to determine whether we control the good or service before it is transferred to the customer or whether we are acting as an agent of the third party. To determine whether or not we control the good or service before it is transferred to the customer, we assess indicators including whether we or the third party is primarily responsible for fulfillment and which party has discretion in determining pricing for the good or service, as well as other considerations. Based on our assessment of these indicators, we have concluded that our promise to our customer to provide our payment services is distinct from the services provided by the card issuing financial institutions and payment networks in connection with payment transactions. We do not have the ability to direct the use of and obtain substantially all of the benefits of the services provided by the card issuing financial institutions and payment networks before those services are transferred to our customer, and on that basis, we do not control those services prior to being transferred to our customer. As a result, we present our revenue net of the interchange fees charged by the card issuing financial institutions and the fees charged by the payment networks. The majority of our processing services are priced as a percentage of transaction value or a specified fee per transaction, depending on the card type. We also charge other per occurrence fees based on specific services that may be unrelated to the number of transactions or transaction value. Given the nature of the promise and the underlying fees based on unknown quantities or outcomes of services to be performed over the contract term, the total consideration is determined to be variable consideration. The variable consideration for our payment processing service is usage-based and therefore it specifically relates to our efforts to satisfy our payment services obligation. In other words, the variability is satisfied each day the service is provided to the customer. We directly ascribe variable fees to the distinct day of service to which it relates, and we consider the services performed each day in order to ascribe the appropriate amount of total fees to that day. Therefore, we measure revenue for our payment processing service on a daily basis based on the services that are performed on that day. Certain of our technology-enabled customer arrangements contain multiple promises, such as payment services (as aforementioned, a series of distinct days of service), perpetual software licenses, software-as-a-service ("SaaS"), maintenance, installation services, training and equipment, each of which is evaluated to determine whether it represents a separate performance obligation. SaaS arrangements are generally offered on a subscription basis, providing the customers with access to the SaaS platform along with general support and maintenance services. Because these promised services within our SaaS arrangements are delivered concurrently over the contract term, we account for these promises as if they are a single performance obligation that includes a series of distinct services with the same pattern of transfer to the customer. In addition, certain installation services are not considered distinct from the SaaS, and are therefore recognized over the expected period of benefit. Once we determine the performance obligations and the transaction price, including an estimate of any variable consideration, we then allocate the transaction price to each performance obligation in the contract using a relative standalone selling price method. We determine standalone selling price based on the price at which the good or service is sold separately. If the standalone selling price is not observable through past transactions, we estimate the standalone selling price by considering all reasonably available information, including market conditions, trends or other company- or customer-specific factors. Substantially all of the performance obligations described above are satisfied over time. Only equipment sales, perpetual software licenses and certain professional services are generally transferred to the customer at a point in time. For certain other professional services that represent separate performance obligations, we generally use the input method and recognize revenue based on the number of hours incurred or services performed to date in relation to the total services expected to be required to satisfy the performance obligation. We satisfy the combined SaaS performance obligation by standing ready to provide access to the SaaS. Consideration for SaaS arrangements may consist of fixed- or usage-based fees. Revenue is recognized over the period for which the services are provided or by directly ascribing any variable fees to the distinct day of service based on the services that are performed on that day. Transaction Price Allocated to Future Performance Obligations ASC 606 requires disclosure of the aggregate amount of the transaction price allocated to unsatisfied performance obligations; however, as allowed by ASC 606, we have elected to exclude from this disclosure any contracts with an original duration of one year or less and any variable consideration that meets specified criteria. As described above, our most significant performance obligations consist of variable consideration under a stand-ready series of distinct days of service. Such variable consideration meets the specified criteria for the disclosure exclusion; therefore, the majority of the aggregate amount of transaction price that is allocated to performance obligations that have not yet been satisfied is variable consideration that is not required for this disclosure. The aggregate fixed consideration portion of customer contracts with an initial contract duration greater than one year is not material. Accounts Receivable, Contract Assets and Contract Liabilities A contract with a customer creates legal rights and obligations. As we perform under customer contracts, our right to consideration that is unconditional is considered to be accounts receivable. If our right to consideration for such performance is contingent upon a future event or satisfaction of additional performance obligations, the amount of revenues we have recognized in excess of the amount we have billed to the customer is recognized as a contract asset. Contract liabilities represent consideration received from customers in excess of revenues recognized. Contract assets and liabilities are presented net at the individual contract level in the consolidated balance sheet and are classified as current or noncurrent based on the nature of the underlying contractual rights and obligations. Net contract liabilities included in accounts payable and accrued liabilities on our consolidated balance sheet were $99.4 million at March 31, 2018 and $100.6 million at January 1, 2018. Contract liabilities included in other noncurrent liabilities on our consolidated balance sheet were $8.1 million at March 31, 2018 and $6.0 million at January 1, 2018. Revenues for the three months ended March 31, 2018 included $40.6 million that was in contract liabilities at January 1, 2018. Net contract assets were not material at March 31, 2018. Contract Costs We incur costs to obtain contracts with customers, including employee sales commissions and fees to business partners. At contract inception, we capitalize such costs that we expect to recover and that would not have been incurred if the contract had not been obtained. We also capitalize certain costs incurred to fulfill our contracts with customers that (i) relate directly to the contract, (ii) are expected to generate resources that will be used to satisfy our performance obligation under the contract and (iii) are expected to be recovered through revenue generated under the contract. At March 31, 2018, we had net capitalized costs to obtain and fulfill contracts of $161.3 million and $7.3 million, respectively, included in other noncurrent assets on our consolidated balance sheet. Contract costs are amortized on a systematic basis consistent with the transfer to the customer of the goods or services to which the asset relates. A straight-line or proportional amortization method is used depending upon which method best depicts the pattern of transfer of the goods or services to the customer. In addition, these contract costs are evaluated for impairment by comparing, on a pooled basis, the expected future net cash flows from underlying customer relationships to the carrying amount of the capitalized contract costs. At March 31, 2018, none of our capitalized contract costs were impaired. In order to determine the appropriate amortization period for contract costs, we consider a combination of factors, including customer attrition rates, estimated terms of customer relationships, the useful lives of technology we use to provide goods and services to our customers, whether future contract renewals are expected and if there is any incremental commission to be paid on a contract renewal. We amortize these assets over the expected period of benefit, which, based on the factors noted above, is typically 7 years. Costs to obtain a contract with an expected period of benefit of one year or less are recognized as an expense when incurred. During the three months ended March 31, 2018, amortization of capitalized contract costs was $10.2 million.

X
- References No definition available. + Details
Name: | us-gaap_RevenueFromContractWithCustomerAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure of revenue from contract with customer to transfer good or service and to transfer nonfinancial asset. Includes, but is not limited to, disaggregation of revenue, credit loss recognized from contract with customer, judgment and change in judgment related to contract with customer, and asset recognized from cost incurred to obtain or fulfill contract with customer. Excludes insurance and lease contracts. + References Reference 1: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 235 -URI http://asc.fasb.org/topic&trid=2122369 Reference 2: http://www.xbrl.org/2003/role/presentationRef -Publisher FASB -Name Accounting Standards Codification -Topic 606 -URI http://asc.fasb.org/topic&trid=49130388 + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | nonnum:textBlockItemType
Balance Type: | na
Period Type: | duration