Since the agreement end users signed/acknowledged will not be sent to Zuora, so if the customer is storing the agreements from end users as any type of data in their own system, they could use field `field_mitConsentAgreementRef` to save an id or any other string to help to link it to Zuora system. (as noted in the document, the id/string should be <= 128 characters). Here are 2 examples of how customer could use it: (Customer: zuora customers, End User: card owners) Example 1: The agreements from end users are being stored as a PDF file(digit copy of the agreement) in customers server under different folders. So the value of `field_mitConsentAgreementRef` could be `Folder: 04122019, File: CustomerName_Agreement_1.PDF` Example 2: The customer is saving a record in their database every time there is an end user acknowledges the agreement. The record has all necessary information about the agreement(e.g. end user id, acknowledged datetime, agreement type...) So the value of `field_mitConsentAgreementRef` could be the id of the record in your database like `kQNsmpIhsXsCONBGHypKttuT` ... View more

Draft This status is only supported with WSDL version earlier than 64. Sample Request { "objects": [ {"AccountId":"2c92c0f9693316890169390e5e8d5349", "Amount":1, "AppliedInvoiceAmount":0, "AppliedCreditBalanceAmount": 1, "EffectiveDate":"2018-10-13T00:00:00", "PaymentMethodId":"2c92c0f9693316890169390e5ea0534d", "Status":"Draft", "Type":"Electronic" }, {"AccountId":"2c92c0f9693316890169390e5e8d5349", "Amount":1, "AppliedInvoiceAmount":0, "AppliedCreditBalanceAmount": 1, "EffectiveDate":"2018-10-13T00:00:00", "PaymentMethodId":"2c92c0f8528dab8a01529be039061dea", "Status":"Draft", "Type":"External" } ], "type":"Payment" }   Processing This status indicates that we didn't get the response after we send the payment request to the payment gateway. When that happens, please refer to the steps in below post to update the payment: https://community.zuora.com/t5/Billing-Payments/How-to-update-the-Stuck-Payment-that-is-on-Processing-status/td-p/8246 Besides, if you'd like to keep the processing payments be better monitored, please refer to below post: https://community.zuora.com/t5/Billing-Payments/How-to-monitor-if-there-is-Payment-Refund-stuck-in-my-tenant/m-p/27259   Processed For electronic payments, this status indicates the payment gateway has returned a positive response to us after we sent the request.  For external payment, this status indicates the payment has been created successfully.   Error For electronic payments, this status indicates the payment gateway has returned a negative response to us after we sent the request.  (This is not an expected status for an external payment.)   Voided For electronic payments, this status is for the payments which successfully voided. (This is not an expected status for an external payment.)   Canceled For external payments, this status is for payments which are successfully canceled. (This is not an expected status for an electronic payment.) ... View more

Here is a table shows the main difference among the different implementations for Vantiv payment gateway integrations:     Vantiv Vantiv (Now Worldpay) Vantiv Payment Gateway, API v8.10 XML version  8.12 12.2 8.10 AVS/CVV filtering configurable Yes No No 3DS supported No Yes No eCheck Verification configurable No Yes No Fraud Tool Kit Support configurable No Yes No need to contact Zuora Support to configure Merchant ID Yes No No                           ... View more

Supported Payment Method for  WorldPay (Corporate Gateway), below are the supported payment methods: Credit Card Debit Card for WorldPay 1.4, below are the supported payment methods: Credit Card CC Reference Transaction Bank Transfer Supported Feature Gateway Reconciliation is only supported by WorldPay 1.4.   Other Info Both of the 2 implementations are using the same DTD version 1.4. ... View more

Mass Payment Upload can be done through API. Here are the steps:   1)get Bearer Token https://www.zuora.com/DEVELOPER/API-REFERENCE/#operation/createToken ysong-macOS:~ ysong$ curl -X POST -H "Content-Type: application/x-www-form-urlencoded" -d “client_id=xxxxxxxxxxx" --data-urlencode "client_secret=xxxxxxxxxxx" -d "grant_type=client_credentials" "https://rest.apisandbox.zuora.com/oauth/token" {"access_token":"xxxxxxxxxxx","token_type":"bearer","expires_in":3599,"scope":"entity.xxxxxxxxxxx platform.write service.genesis.read service.genesis.write service.usage.delete service.usage.update service.usage.write tenant.xxxxx user.xxxxxxxxxxx","jti":"xxxxxxxxxxx”} 2) prepare the CSV file for uploading https://knowledgecenter.zuora.com/CC_Finance/Mass_Updater/Mass_Payment_Upload (a sample upload file will be attached with this message) 3) perform mass action https://www.zuora.com/DEVELOPER/API-REFERENCE/#operation/POST_MassUpdater ysong-macOS:Desktop ysong$ curl -X POST -H "Authorization: Bearer xxxxxxxxxxx" -F "file=@test_mass_payment_upload.csv" -F "params={\"actionType\": \"MPU\"}" "https://rest.apisandbox.zuora.com/v1/bulk" { "success" : true, "bulkKey" : "2c92c0fa6924505001692a45829f2b5f" } 4) Get mass action result ysong-macOS:Desktop ysong$ curl -X GET -H "Authorization: Bearer xxxxxxxxxxxx" -H "Content-Type: application/json" "https://rest.apisandbox.zuora.com/v1/bulk/2c92c0fa6924505001692a45829f2b5f" { "actionType" : "MPU", "inputSize" : 2294, "uploadedBy" : "ying.song+ar@zuora.com", "uploadedOn" : "2019-02-26 06:46:32", "status" : "Completed", "startedOn" : "2019-02-26 06:46:32", "endedOn" : "2019-02-26 06:46:34", "outputSize" : 595, "outputURL" : "https://apisandbox-api.zuora.com/rest/api/file/2c92c08569244b5501692a458b5b0e19", "outputType" : "(url:.csv.zip)", "totalCount" : 17, "processedCount" : 17, "errorCount" : 0, "successCount" : 17, "success" : true } 5)if there are failed records, get the result file to find out the reason why failed e.g.   =Some Common Errors= External payment can use only external payment method. -> this will happen when column “PaymentType" and "Billing Account ID" are not specified  Account id cannot be null for electronic payments. -> this will happen when “PaymentType=Electronic Payment” without specifying “Billing Account ID”  For electronic payment, effective date should be today's date or the payment should fail. -> this will happen if “PaymentType=Electronic Payment” while payment date is not today’s date gatewayId must be specified in order to create an electronic payment. -> this will happen if “PaymentType=Electronic Payment” without specifying “Gateway ID" ... View more

First, below are the browser types officially supported by Zuora. Mozilla Firefox: Two most recent stable major versions Google Chrome: Latest stable version Microsoft Internet Explorer: Three most recent stable major versions https://knowledgecenter.zuora.com/BB_Introducing_Z_Business/Policies/Browser_Support_Policy If you're already using one of above browsers(Desktop) and still couldn't have the drop-down list loaded, we would suggest to try following steps: 1) try again with clearing browser's cache https://support.google.com/accounts/answer/32050?co=GENIE.Platform%3DDesktop&hl=en 2) try with different browsers from the same device 3) try with the same browser but from a different device (If the issue only happens a to certain device, then it is quite possible to be a client-side issue) ... View more

You could use our Scheduled Reporting feature and below are the detailed steps to configure one: 1) goto Reporting 2) select Payment as the reporting object (or select Refund if you'd like to get a list of Processing Refunds report) 3) Click Detail to create a detail report 4) Edit the Filters to filter payments with a status of "Processing", change the range you'd like to monitor(e.g. is equal to today for daily monitoring) 5) Save the Report  6) click the little arrow beside of "Save Report & Run" then click "Schedule"  7) Schedule the report as below if you need a daily report or change according to the requirement. ... View more

On GoCardless side, only EUR Bank Account supports to use "sepa_core" scheme when creating mandate with IBAN. For GBP Bank Account, specifing "sepa_core" when creating the mandate will cause validation error as below:   And if no valud specified for scheme in the request, scheme "Bacs" will be used automatically. So the answer to the question is: it is not supported to  create a payment method using "sepa_core" scheme on GoCardless side with a GB IBAN. On that point, our payment method type "BankTransfer - SEPA" is not being mapped to GoCardless' "sepa_core" scheme perfectly and we will improve our document to help address the confusion. ... View more

The 30 character limit is a limit to basic bank number which is applied to below payment methods: BankTransfer - Direct Debit (NZ) BankTransfer - Direct Debit (UK) BankTransfer - Direct Entry (AU)   And when using IBAN to create Bank Transfer payment method, we could specify the BankTransferType to be SEPA and that will make the length limitation on BankTransferAccountNumber turn to 42, which means currently maximum length for IBAN is supported with this field.   Above has been tested with GoCardless payment gateway and our document in KC will to updated soon. ... View more

For Bank Transfer Type `DirectDebitUK`(BACS) passing "AccountNumber + BankCode/SortCode" is supported.   Here is an example of how to do it with REST API:   Payment Gateway: GoCardless Payment Method Type: Bank Transfer(SEPA) REST API Request:  POST https://rest.apisandbox.zuora.com/v1/object/payment-method { "AccountId": "2c92c0f9671686a201672f0ba1864f47", "BankTransferAccountNumber": "55779911", "BankCode": "200000", "BankTransferAccountName": "Test", "Email": "test@gmail.com", "FirstName": "test", "Country": "United Kingdom", "LastName": "test", "Type": "BankTransfer", "BankTransferType": "DirectDebitUK" } ... View more