About Rolando

Rolando

In the upcoming Zuora Release R247 we’re moving Zuora Dashboard from “Reporting” (in the left navigation menu) to a new section we’re calling “Analytics”. To learn more about Zuora Dashboard, please visit: https://knowledgecenter.zuora.com/CD_Reporting/AA_Dashboard If you encounter any issues with this update, please contact Zuora Support. Thank you! Zuora Analytics Team

Rolando · ‎04-10-2019

Not necessarily, you may continue using Oauth where supported. It is entirely up to you on how you want to authenticate. The key point for this post is that Oauth is not supported in the Production Copy (Services) environments.

Rolando · ‎04-09-2019

Zuora Reporting and Insights Analysis will undergo maintenance for US Production environment only, Saturday April 20th 2019, 6:00 PM - 8:00 PM PT During the maintenance window, Reporting and Insights Analysis may appear to be running, but no report changes can be saved and no report runs can be processed. Further, any reports scheduled during the downtime will be executed immediately after the downtime ends.

Rolando · ‎03-27-2019

Zuora Reporting and Insights Analysis will undergo maintenance according to the following schedule: Performance Test Environment (PT1/PTE) ▪ Wednesday April 3rd 2019, 5pm-6pm PT - Insights Analysis ▪ Thursday April 4th 2019, 5pm-6pm PT - Reporting and Insights Analysis US API Sandbox ▪ Saturday April 6th 2019, 6pm-8pm PT - Reporting and Insights Analysis US Production ▪ Sunday April 7th 2019, 6pm-8pm PT - Reporting and Insights Analysis During the maintenance window, Reporting and Insights Analysis may appear to be running, but no report changes can be saved and no report runs can be processed. Further, any reports scheduled during the downtime will be executed immediately after the downtime ends.

Rolando · ‎03-11-2019

For the CyberSource Payment API v2.0 setup, this is the expected behavior. As noted in our Cybersource Payment Gateway knowledge center documentation... For CyberSource, Payment API v2.0, you must copy the key content in text and paste it to the Private Key field. To obtain the private key for CyberSource, Payment API v2.0, complete the following steps: 1. Log in to Cyber Source Business Center. 2. In the left navigation pane, click Account Management > Transaction Security Keys. 3. Click Security Keys for the SOAP Toolkit API. 4. On the Security Keys for the SOAP Toolkit API page, click Generate Key. You can view the content of the key. 5. Copy the whole key string and paste it to the Private Key field on the New Gateway page.

Rolando · ‎03-11-2019

In my payment gateway setup for CyberSource Payment API v2.0, there is no CHOOSE FILE button for selecting the private key .p12 file like the setup for CyberSource Enterprise Gateway, API v1.97.

Rolando · ‎02-26-2019

UPDATE: We have no current plans to deprecate the payment export at this time. Therefore, until we announce a more comprehensive replacement, the existing export will remain available. For the time being, please disregard the popup messaging until we can get it updated or removed.

Rolando · ‎02-13-2019

We have a Customer Solutions Article which provides the steps needed to self-resolve "Payments stuck in processing status". Please check out the article here: http://community.zuora.com/t5/Billing-Payments/How-to-update-the-Stuck-Payment-that-is-on-Processing-status/m-p/8246/highlight/true#M405 If you have any questions regarding this process please feel free to reply back directly to this ticket. You may also reply back directly on the article to solicit a response from other customers and Zuora support staff.

Rolando · ‎01-17-2019

Zuora Dashboard features will undergo maintenance on Friday 01/18/2018 from 06:00 PM - 06:30PM PT in the US Production environment only. During the maintenance downtime, Dashboard won’t be available to customers. EU Production, US API Sandbox, and EU API Sandbox environments are not affected by this maintenance. Information on the Zuora Dashboard can be found here: https://knowledgecenter.zuora.com/CD_Reporting/AA_Dashboard

Rolando · ‎01-16-2019

Our current implementation does not support CAPTCHA to be triggered in this manner. It can only be triggered after at least 1 failed attempt.

Rolando · ‎01-16-2019

For CAPTCHA, we understand that the “Limit the Number of Payment Page Submissions before CAPTCHA Challenge” setting can be set to 0 to disable CAPTCHA completely or use number X to indicate that the CAPTCHA will populate after X attempts. However, we want CAPTCHA to populate right as the initial iFrame session starts without any attempts/submissions. Is this supported?

Rolando · ‎11-12-2018

UPDATE: The maintenance was completed successfully within the specified window. Our apologies for the delayed response.

Rolando · ‎10-24-2018

5. What will Payment Application look like when I unapply a payment? This will depend on the use case as well. Below are several examples to help describe how it will look: 1. Fully unapply payment from invoice: a. generate invoice with $100 > INV-001, balance: $100 b. create a payment (PAY-001) with amount $100 and apply to the invoice INV-001 with $100 at the same time c. ONE payment application would be generated: PA-001, apply amount: $100, Source Payment: PAY-001, Target Invoice: INV-001 d. as a result, unapplied amount on payment is $0. e. unapply the payment( PAY-001) with amount $100 from invoice INV-001 f. TWO payment applications would be generated: PA-002, apply amount: -$100, Source Payment: PAY-001, Target Invoice: INV-001 PA-003, apply amount: $100, Source Payment: PAY-001, Target Invoice: n/a d. as a result, unapplied amount on payment is $100 which is tracked by PA-003. 2. Partial unapply payment from invoice: a. generate invoice with $100 > INV-001, balance: $100 b. create a payment(PAY-001) with amount $100 and apply to the invoice INV-001 with $100 at the same time c. ONE payment application would be generated: PA-001, apply amount: $100, Source Payment: PAY-001, Target Invoice: INV-001 d. as a result, unapplied amount on payment is $0 e. unapply the payment (PAY-001) with amount $80 from invoice INV-001 f. TWO payment applications would be generated: PA-002, apply amount: -$80, Source Payment: PAY-001, Target Invoice: INV-001 PA-003, apply amount: $80, Source Payment: PAY-001, Target Invoice: n/a d. as a result, unapplied amount on payment is $80 which is tracked by PA-003. 6. How to refund a payment? When the Invoice Settlement feature is enabled, only the' unapplied amount' can be refunded. For example: a. If a payment of $100 is created but not applied to any invoice, then the unapplied amount is $100. As a result, the merchant can refund up to the entire amount of $100. b. If a payment of $100 is created and $20 is applied to an invoice, then the 'unapplied amount' is $80. As a result, only $80 can be used for refund.

Rolando · ‎10-24-2018

To help understand how the datasource works, you will need to understand how the Invoice Settlement model works in regards to a refund or chargeback operation. Please review the following: 1. What is Payment.UnappliedAmount? The amount that you (the 'merchant') owe to the customer. 2. How to create a payment with unapplied amount? You can create a payment without specifying an invoice or debit memo. Or you can unapply a payment from an invoice or debit memo. The amount will go to 'unapplied amount'. 3. What is 'Payment Application'? Payment Application is used to track the amount change on a Payment and the balance change on the target document- like Invoice or Debit Memo. There are two types of Payment Application: Payment Application with Invoice or Debit Memo info; Payment Application without Invoice or Debit Memo info. For the first type A, it tells what payment is applied to an invoice or debit memo and the payment amount. For the second type, it indicates the amount that gets changed on the Unapplied Amount of Payment. The Payment Application cannot be created directly, it is generated by a payment operation, like `creation`, `apply` or `unapply`. 4. What will the Payment Application look like when a payment is created? This will depend on the use case. Below are several examples to help describe how it will look: 1. Create a payment and fully apply to the invoice: a. generate invoice with $100 > INV-001, balance: $100 b. create a payment (PAY-001) with amount $100 and apply to the invoice INV-001 with $100 at the same time c. ONE payment application will be generated: PA-001, apply amount: $100, Source Payment: PAY-001, Target Invoice: INV-001 d. as a result, unapplied amount on payment is $0. 2. Create a payment and partially apply to the invoice: a. generate invoice with $100 > INV-001, balance: $100 b. create a payment (PAY-001) with amount $100 and apply to the invoice INV-001 with $80 at the same time c. TWO payment applications would be generated: PA-001, apply amount: $80, Source Payment: PAY-001, Target Invoice: INV-001 PA-002, apply amount: $20, Source Payment: PAY-001, Target Invoice: n/a d. as a result, unapplied amount on payment is $20 which is tracked by PA-002. 3. Create a payment and don't apply to any invoice: a. create a payment (PAY-001) with amount $100 and do not apply to any invoice. b. ONE payment application would be generated: PA-001, apply amount: $100$, Source Payment: PAY-001, Target Invoice: n/a d. as a result, unapplied amount on payment is $100 which is tracked by PA-001. (continued on next reply)

Rolando · ‎10-24-2018

We have some questions about how the 'Payment Application' Datasource works when the Invoice Settlement feature is enabled. Specifically, when using this datasource to run reports and exports we have noticed that there are additional row/lines for a single Payment that was refunded- with this logic we should only see 2 rows/lines but we are noticing a 3rd row/line. We need help understanding the logic behind how the 'Payment Application' Datasource works.

Rolando · ‎10-19-2018

Zuora Insights and Dashboard features will undergo maintenance on Saturday 10/27/2018 from 06:00PM - 08:00PM PT in the US Production environment only. During the maintenance downtime, Insights Dashboard won’t be available and Zuora Insights might appear to be running but will return errors when trying to save changes or when exporting data. US APISandbox, EU Production, and EU APISandbox environments are not affected by this maintenance.

Rolando · ‎10-17-2018

To see who last updated the report, go to the report and EDIT. Next to the report name you will see a small dropdown arrow... click on the arrow to reveal the details which includes the user who last updated the report.

Rolando · ‎10-17-2018

For auditing purposes we need to verify who last updated a report in the Reporting feature. We see who the report Creator is and the 'Last Updated' dateTime but no details as to who updated it on that date.

Rolando · ‎10-11-2018

Zuora has the ability to report on ALL entities at the parent level utilizing the entity selector. Therefore, you can rebuild the 4 reports at the parent entity level and select all entities to see all results from all entities in one report. You can read more about multi-entity selector reporting here: https://knowledgecenter.zuora.com/Insights/A_Quick_Reference/AC_Insights_Analysis#Multi-entity_Reporting

Rolando · ‎10-11-2018

We have 5 entities that each have 4 Insights Analysis reports that are used frequently. When our business team reconciles these reports, they have to manually combine the reports of same type across entities and it requires lot of manual efforts. Please advise how can we achieve this consolidation within Zuora.

Rolando · ‎10-11-2018

This error means that First Data is declining the transaction- specifically "Blocked for suspicious activity." The reason the gateway is detecting fraud is because during testing, you are using the same test card number too many times to be classified as fraud. For more information please follow up with your First Data merchant support representative.

Rolando · ‎10-11-2018

We configured 'FirstData Ucom Gateway'. During testing, we are unable to make a payment using this gateway. The error message in Zuora is '269801 -- No Gateway Messsage Received'.

Rolando · ‎10-01-2018

(Opening this Ideas RFE on the behalf of a customer) Request to increase the character limit for Invoice Comments. It currently taps out at 255 characters. We run into this error often when we need to document/include specific invoice information for our clients. This was previously requested on PMT-1886.

Rolando · ‎09-14-2018

Zuora Insights and Dashboard features will undergo maintenance on Saturday 09/15/2018 from 11:00PM - 11:59PM PT in the US Production environment only. During the maintenance downtime, the Insights Dashboard feature won’t be available and the Zuora Insights feature might appear to be running but will return errors when trying to save changes or when exporting data. No other environments are affected by this maintenance.

Rolando · ‎09-06-2018

The Under Review status is triggered by Authorize.Net as you can review in Authorize.Net eCheck userguide here: https://www.authorize.net/content/dam/authorize/documents/echecknetuserguide.pdf. Zuora has no control over ACH payments placed on hold by the payment gateway. This would not have anything to do with the Customer Account or Payment Method setup. This issue is purely gateway-related. Unfortunately Zuora has no visibility into why certain ACH payments process through quickly or placed on hold. This would be something to review with Authorize.Net's merchant support team. This may also have to do with any Advanced Fraud Solutions you may or may not subscribe to with Authorize.Net.

Rolando · ‎09-06-2018

I have a customer who pays via ACH auto payment. Each month it errors out. When I look in Authorize.net it is in a review status. It eventually moves to settled successfully. Is the review status something on the bank side? I have many other customers who pay via ACH auto pay and this is the only one that errors. I have looked over the account and it appears to be set up identical to other ACH auto pays. Is it something in the account?

Rolando · ‎08-29-2018

Zuora Insights and Dashboard features will undergo maintenance on Friday 08/31/2018 from 5:00PM - 07:00PM PT in US API Sandbox environment only. During the maintenance downtime, Dashboard won’t be available and Insights might appear to be running but will return errors when trying to save changes or when exporting data. US Production environments are not affected by this maintenance.

Rolando · ‎08-24-2018

Zuora does not place any restrictions on processing limits. This restriction is at the payment gateway level. When a company sets up a payment gateway merchant account, a ceiling limit is set by their underwriting/risk department. You will need to have someone from your organization (who has the details about the merchant account like business tax ID, etc) contact the payment gateway's merchant services department to discuss raising the ceiling limit on your merchant account/s.

Rolando · ‎08-24-2018

Is it possible to raise the limit on our credit card payments?

Rolando · ‎08-20-2018

Our Zuora payments team will be handling those changes on our end. No further actions or changes are required for our customers.

Happy Business Starts Here