I've already had my HPM form translation configured and it is working as expected Why the words in the Captcha window is still using English? ... View more

Before customers enable Invoice Settlement, they could use the data source RefundInvoicePayment to get the mapping between Refund and Invoice directly Refund Invoice Payment Data Source   But once Invoice Settlement is enabled, they will have to do two export on RefundPart and PaymentPart and join the export result out of Zuora to get the same result.   So if we could have data source RefundInvoicePayment back, it will be much easier for the customers who have been using it before enabled Invoice Settlement. ... View more

If you're seeing duplicate payment methods got created by clicking the submit button for multiple times, please check if you've  removed  pointer-events: none;  from the CSS rule  .btn-submit.disabled ... View more

For a general case, you will need to: 1) get the list of payments you'd need to operate with the value of fields might be needed in the later steps 2) bulk void/refund the payments ("Void" transaction might not be supported by the payment gateway where the payment processed and it might also fail if it’s already passed the time limit when a void transaction is acceptable by the payment gateway. For those 2 cases, please use refund payment to complete the charge back) 3) (if needed) change the customer accounts' default payment gateway 4) bulk create payments again (main operations here are using API as an example, but API is not the only approach we have)   DSE filter to find out payments Data Source [Invoice Settlement not enabled] Invoice Payment [Invoice Settlement enabled] Payment Application Fields Account: ID, Payment Gateway Name Invoice: ID, Balance Payment: Amount, Gateway, ID, Payment Number, Status, Type Payment Method Snapshot: Credit Card Type, Payment Method ID, Type Filters Payment.Status=Processed Payment.Type=Electronic (adding other filters customer needs) Time Frame (select the required time frame)   Void Payment https://www.zuora.com/developer/api-reference/#operation/Action_POSTupdate   PUT https://rest.apisandbox.zuora.com/v1/action/update {   "objects": [     {       "Id": "2c92c0f8707b709e01707f5ee8b6359e",       "Status": "Voided"     },     {       "Id": "2c92c0f8707b70a401707f5c3cbe7591",       "Status": "Voided"     }   ],   "type": "Payment" }     Refund Payment https://www.zuora.com/developer/api-reference/#operation/Action_POSTcreate   POST https://rest.apisandbox.zuora.com/v1/action/create { "objects": [ {"AccountId": "2c92c0f969051fe301690ac8c2c520a0", "Amount": 5, "Comment": "this is comments", "PaymentId": "2c92c0f8709a185601709e1e99d87762", "ReasonCode": "Standard Refund", "RefundInvoicePaymentData": { "RefundInvoicePayment": [] }, "SourceType": "Payment", "Type": "Electronic" }, {"AccountId": "2c92c0f9555cf11d0155761484d2576f", "Amount": 5, "Comment": "this is comments", "PaymentId": "2c92c0f8709a185601709e1e9a38776b", "ReasonCode": "Standard Refund", "RefundInvoicePaymentData": { "RefundInvoicePayment": [] }, "SourceType": "Payment", "Type": "Electronic" } ], "type":"Refund" }   Batch update customer account gateway https://community.zuora.com/t5/Billing-Payments/How-to-bulk-update-customer-account-s-payment-gateway/td-p/30173   Create Payment https://www.zuora.com/developer/api-reference/#operation/Action_POSTcreate POST https://rest.apisandbox.zuora.com/v1/action/create { "objects": [ {"AccountId":"2c92c0f969051fe301690ac8c2c520a0", "Amount":10, "AppliedInvoiceAmount":10, "AppliedCreditBalanceAmount": 0, "EffectiveDate":"2018-10-13", "PaymentMethodId":"2c92c0f9709a26d801709e16d7e40755",  "InvoiceId":"2c92c0996905120701690ae084e22dd4", "Status":"Processed", "Type":"Electronic" }, {"AccountId":"2c92c0f9555cf11d0155761484d2576f", "Amount":10, "AppliedInvoiceAmount":10, "AppliedCreditBalanceAmount": 0, "EffectiveDate":"2018-10-13", "PaymentMethodId":"2c92c0f85d3a5d65015d3aba32ff77aa",  "InvoiceId":"2c92c0945e5e74b8015e6f7cc01b1627", "Status":"Processed", "Type":"Electronic" } ], "type":"Payment" }     ... View more

When using PayPal Gateway Reconcialation, you may find that the gateway state of some payments stay at "Submitted" although they were settled on the payment gateway side.   One possible reason is that there was refund created on the payments within 7 days after the payment got created.   With our current design,  the payment transactions that take place on day N will be reconciled only once by Zuora on day N+7, and "Refunded" is not one of the supported reconciliation events. https://knowledgecenter.zuora.com/Zuora_Central/Billing_and_Payments/M_Payment_Gateways/Supported_Payment_Gateways/PayPal_Express_Checkout_Gateway ​ ​So on the N+7 day, when we retrieved a status of Refunded for the payments, it is considered as an Unknown event type and no action was taken, so the GatewayState of the payments has been left as Submitted. ... View more

Please make sure to first test in the Sandbox environment before making any change to the Production environment.   1. Prepare the list of payments to need to be updated If you'd like to settle all payments with Submitted as GatewaState, it could be done through Data Source Export: open the exported file, copy all the records and paste into a text editor, update the 1st line from "Payment: ID" to "ID" save from the text editor with encoding LF   2.   Use REST API client tool for bulk operation Many of the REST API client tools(e.g. Postman) have the feature to help customers execute REST API requests in bulk. 1) create an update request under a collection, make payment id in the URL to be input params I've left the request body as {} since no param is required, but please add the ones needed according to the API reference here for  API request: Settle Payment 2) start Postman's Collection Runner and  select the Collection where your request is saved, select the file generated from 1 to be the Data File, start run     Reference: Starting a collection run Looping through a data file in the Postman Collection Runner ... View more

We could use Reporting to get a summary report of payment method authorization results. Here is an example of how to configure it:   1) Log in to your tenant and go to Reporting > Reporting   2) Click button "Crete New Report"   3) Type "Payment Method Transaction Log" in the input field and select the one displayed as the search result   4) Configure the Summary Report as below: Note: A) The Payment Gateway Name "My Payment Gateway" is an example name. Please replace it with the payment gateway name you'd like to check. B) The response code "Approved" and "Declined" are 2 example response code. Please define which response codes are considered as a positive response and which response codes are considered as a negative response and specify accordingly. (Different Payment Gateways are using different response codes)   5) Save the report and run it to get the result. 6) We could also make the report to be a scheduled job and sending results to configured email addresses like below: And please more detailed instruction of how to schedule a report run in the below document: https://knowledgecenter.zuora.com/CD_Reporting_And_Analytics/B_Using_Reporting/B_Schedule_Report_Runs ... View more

For most cases, the payment gateway will provide test card numbers for merchants to conduct positive/negative testing.  And it is always highly recommended to first test the same payment gateway in your Zuora Sandbox tenant before going live with it in your Production tenant.   As a side reference, here are the links about the test card numbers provided by some of the payment gateways:   Bambora Payment Gateway(IP Payments Payment Gateway): https://dev-apac.bambora.com/checkout/guides/get-up-and-running/test-your-setup Adyen: https://docs.adyen.com/development-resources/test-cards/test-card-numbers/ Braintree: https://developers.braintreepayments.com/guides/credit-cards/testing-go-live/java CyberSource: https://developer.cybersource.com/hello-world/testing-guide.html https://support.cybersource.com/s/article/How-does-one-simulate-various-error-messages-in-the-CyberSource-test-environment Stripe: https://stripe.com/docs/testing Vantiv: http://vantiv-ecommerce.github.io/sandbox/ First Data Payeezy: https://support.payeezy.com/hc/en-us/articles/204504235-Using-Test-Credit-Card-Numbers BlueSnap: https://developers.bluesnap.com/docs/test-credit-cards https://support.bluesnap.com/docs/test-credit-card-numbers Chase Paymentech: http://directconnectps.com/wp-content/uploads/2016/09/Chase-Paymentech-Test-Conditions-v1.1.3-2016.09.21.pdf GoCardless: https://developer.gocardless.com/getting-started/developer-tools/test-bank-details/ https://support.gocardless.com/hc/en-us/articles/360000984225-Test-bank-details Ingenico: https://payment-services.ingenico.com/int/en/ogone/support/guides/user%20guides/test-account-creation/test-transactions https://payment-services.ingenico.com/int/en/ogone/support/guides/integration%20guides/split-credit-debit-cards/testing Merchant e-Solutions: https://developer.merchante-solutions.com/#/payment-gateway-testing WorldPay: http://support.worldpay.com/support/kb/bg/testandgolive/tgl5103.html PayPal: https://developer.paypal.com/docs/classic/payflow/payflow-pro/payflow-pro-testing/ https://developer.paypal.com/docs/classic/payflow/express-checkout/testing/ https://developer.paypal.com/docs/classic/payflow/integration-guide/test-transactions/   But since the links are gathered from online search by Zuora Support Team without actual testing one by one, so please also double confirm with the payment gateway to verify if these should be the cards used for testing with your account and if it is the latest version you should use.    And if you found any of the links are invalid or you have found better links, please feel free to leave a comment under this thread so the information could be shared with other customers as well. Thanks!! ... View more

Question: When testing 3DS2 integration with CyberSource and noticed that the challenge window flashed and disappeared, no chance to input password but the payment method got successfully created. Why is that?   Answer:  The blank flash challenge window is expected behavior for the below case: payerAuthEnrollReply_authenticationPath RIBA_PASS The card-issuing bank supports risk-based authentication, and it is likely that the cardholder will not be challenged to provide credentials; also known as silent authentication. This has been explained in Cybersource's below document on Page 220: http://apps.cybersource.com/library/documentation/dev_guides/Payer_Authentication_SCMP_API/Payer_Authentication_SCMP_API.pdf ... View more

For payments failed with error message "Processing Failed", if we use Data Source Export to get the ResponseString of the Payment transaction, we could see the ResponseString is blank.   For payments failed like this, it means  Zuora has received the response(failed) but the field gateway used to populate the error code is blank. So we are using a generic process failed status. ... View more

Here is the document of the Data Query feature: Data Query   To find all records having a null value of a custom field and all records having a certain value of a custom field, we could use below 2 requests: Submit data query Get data query job   And here is an example test.   Submit the query: POST https://rest.apisandbox.zuora.com/query/jobs {   "compression": "NONE",   "output": {     "target": "S3"   },   "outputFormat": "JSON",   "query": "Select Id, CustomField1__c From CreditMemo where CustomField1__c is null or CustomField1__c='APPSPACE.US'" } {   "data": {     "id": "367897cd-7bbf-4b43-b889-93adad20baef",     "query": "Select Id, CustomField1__c From CreditMemo where CustomField1__c is null or CustomField1__c='abcdefg'",     "queryStatus": "accepted",     "remainingRetries": 3,     "retries": 3,     "updatedOn": "2019-10-31T13:28:06.022Z"   } }   Get the query job: GET https://rest.apisandbox.zuora.com/query/jobs/367897cd-7bbf-4b43-b889-93adad20baef {   "data": {     "id": "367897cd-7bbf-4b43-b889-93adad20baef",     "query": "Select Id, CustomField1__c From CreditMemo where CustomField1__c is null or CustomField1__c='abcdefg'",     "queryStatus": "completed",     "dataFile": "https://owl-auw2-sbx01-query-result.s3.us-west-2.amazonaws.com/367897cd-7bbf-4b43-b889-93adad20baef_7315050230754387.json?X-Amz-Security-Token=FQoGZXIvYXdzEN3%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaDKAFIoLRBfTCo94MZSKVBBomUjfRM6wywG2hP3WmmBFNgV1ZN7PAKhAobIRQizjG7smIxgqvUghaYj9tZypUdAbNqhvMv2Zl8AlVF9ln5yneD%2FcIg%2BcTurco7L3wwVHCmZXJx%2FTF4ra92ES3yuA7sJ7uIlixqdOrvhDPmGsrogfF89xSoLNkY4DdVXDwxyc%2BkA5Am0xs9bFxP%2FLTE1clrajb5Q01aRLyaTx8Iu0Ot9hlPi9P9JnXUY%2FE219sBXI6XPU0iVy%2FGoVt%2BLqM%2FT9JvOK7lupsGJLULAVUkWvwF6XBD0jh6R0HDdht2HtftfabAYRWgDYhikiIwsBptTkYVVMXetej5fpSz7rHWbbCI5jBsioW6Id%2B79Ptnet5x5QRsXmdBxpRZHmvQ0%2BodCw262rL%2B6yJXEi%2FFK6ul%2FhMqSdYQZBGfIN95Fi2fV0TMjEJPzxeE7r88%2FBuVi9GF25zml9PtEcHjyFImPX8WZBHICekvLndfo8JAVtaDjVrJpQo2G11lEyQcVItfIjSN6dzJySCL7MqSXrFIDDs96uJCDR3nPoxg5VVeb94sWDhL9TY%2BKJminquDlAGWkvsRncVvIrXnSWTG3pqQEaDf8r6sRNrl5WEPEgEs5bmfXqunoInerGW68kRpe2uIhfjmvLn8FWNO9MdUxhPDoCJjD82%2BOJlKXSXvbfpHLVM0zuQmTEaX8oYjw%2Ft0EJUTlJODft58C3eCZa9KLaX6%2B0F&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20191031T132807Z&X-Amz-SignedHeaders=host&X-Amz-Expires=604799&X-Amz-Credential=ASIAQXFLO6OTDH35BEOM%2F20191031%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Signature=e840fe0862737a24ed22c994ae61beabcb579d0b1f068c4fb5a6195e419d69f3",     "outputRows": 12,     "processingTime": 1201,     "remainingRetries": 3,     "retries": 3,     "updatedOn": "2019-10-31T13:28:07.223Z"   } }   Fetch the dataFile with the URL in the response of query job and here is its content: ... View more

How to create Stored Credential Profile for Payment Method? Approach 1: create Stored Credential Profiles together with creating new payment methods The stored credential profile could be created together with the payment method through different ways depending on how you're creating payment methods: through UI: Manage stored credential profiles for credit cards through SOAP API: PaymentMethod through REST API: Create payment method, Create credit card payment method through HPM: Add a Checkbox for Stored Credential Consent, Direct POST Fields for Stored Credentials Approach 2: create Store Credential Profiles for existing payment method For the payment methods already existing in your tenant, you could have credential profiles created for them as well. through CIT/MIT Configuration Setting: Migrate all existing payment methods for stored credential transactions   What is the difference between the 2 approaches? (The explanation here is mainly for Stripe v2 Payment Gateway inplementation, could be used as reference for other gateway implementations)  The major difference between these 2 approaches is  we're using different features/requests provided by the payment gateways to get the necessary info to create an active profile for the payment method. To explain it in a simple way, the payment gateway requests we're calling under the 2 approaches are as below(might differ among different payment gateway implementations): Zuora Scope Payment Gateway Scope "CIT/MIT configuration setting" to handle existing Payment Method CIT request provided by Payment Gateway for existing cards checkbox/setAgreement function to handle new Payment Method grandfathering request provided by Payment Gateway for newly created cards   Are both of the approaches required? Can I just use one of them? Both of them are required.   What will happen if I take no action on this? If no action has been taken on this, then when it becomes a must for all transactions to be compliant with the Stored Credential Transaction framework, it is possible that: - for newly created payment methods, payment method creation might fail - for existing payment methods, the payment transaction might fail (since it is not decided by Zuora to approve or decline the transactions, so above is our understanding of the Stored Credential Transaction framework)     Please also refer to the entrance page of this feature in our Knowledge Center for more details: Stored credential transactions ... View more

Issue Description: When trying to refund a credit memo, below error has been returned The transaction CreditMemo with id xxxxxxxxxxxxxxxxxx has been locked by another transaction, you may have to wait for sometime and try again later. But under the credit memo, there is no any related transaction displayed.   Root Cause: There is a known issue that Processing refund will not be displayed in UI under the Credit Memo. So if there is already an electronic refund created on the Credit Memo and the refund has been stuck at the status of Processing, the Credit Memo will be locked and cannot be seen from the Credit Memo UI.    Workaround: When the above error happens, please wait for a while and try the refund operation again. If you're still seeing the same error after 5 minutes, there is a big chance that you've encountered this issue. To find out the previous refund which stuck at Processing status, you could try either of the below methods:   A. check for Processing Refund record from the refund list of the customer account https://www.zuora.com/apps/ARRefund.do?method=list&customer_id=xxxxxxxxxxxxxxxxxxx (please replace 'xxxxxxxxxxxxxxxxxxx' with the Customer Account id)   B. export refund with below filter through Data Source Export   After the Processing refund is located, please refer to below post to update its status to set it to its real status: https://community.zuora.com/t5/Billing-Payments/Refund-Stuck-in-Processing-status/td-p/15851   Internal Ticket Number(for tracking): SET-2383 ... View more

(text in blue: attributes from Stipe, text in green: params from Zuora)   With Stripe v1, the decline_code returned by the Stripe payment gateway is being used as GatewayResponseCode of the Payment in Zuora and there was a known issue that the decline_code could not be completely saved because of the length limitation of GatewayResponseCode. e.g.   With Stripe v2, this has been fixed. The ResponseCode returned by the Stripe payment gateway is being use as GatewayResponseCode of the Payment in Zuora and type, code, decline_code (if there is any) returned by the Stripe payment gateway will be saved within GatewayResponse of the Payment in Zuora to provide more information about declined reason to customer. e.g.   If you're migrating your payment gateway from Stripe v1 to Stripe v2 and there is integration relying on the value of Payment.GatewayResponseCode, please refer to above to make necessary update to your integration.   Please refer to below documents from Stripe payment gateway for more information about the ERROR attributes returned by Stripe payment gateway. https://stripe.com/docs/api/errors#errors-decline_code https://stripe.com/docs/declines/codes ... View more

The 2 types are different on how they could be used in creating payment method as below   1. Create Payment Method through UI Payment Gateway Type Supported Payment Method Type Email Required? PayPal Payflow Pro Express Checkout Yes PayPal Express Checkout Native Express Checkout No   2. Create Payment Method through API Payment Gateway Type Supported Payment Method Type Email Required? PayPal Express Checkout Express Checkout Yes Native Express Checkout No PayPal Payflow Pro Express Checkout Yes   Reference Links: API Reference - Create Payment Method How do I use the PayPal BAID Payment Method in Zuora?       ... View more

Log into your Zuora tenant and go to the Hosted Pages list page   If there is a column of Version in the page list, please make sure the HPM instance you're using is on 2.0 e.g.   If there is no column of Version in the page list, it means all of your HPM instances are on v2.0 e.g. ... View more