Direct POST Form Fields for Payment Pages 2.0
Learn how to customize your Payment Page using HTML Direct POST form fields, including options for cardholder initiated transactions within or outside Zuora.
When constructing a Payment Page form via HTML Direct POST, use the fields in this article to customize your Payment Page. You specify the fields as an HTML <input> elements, where the name attribute is set to the field name shown in the below tables. For example:
<input type="text" name="field_creditCardHolderName" value="<[cardholder name]>"/>
For more detailed information, see Construct Your HTML Form for Direct POST.
Direct POST Fields for Stored Credentials
Zuora gives you the flexibility to perform cardholder initiated transactions (CITs) within or outside Zuora.
If you want to leverage Zuora to perform CITs, include the following fields in the Payment Page 2.0 form. Zuora will perform the credit card validation, and create a stored credential profile within the created payment method if it is valid. For more information about stored credential profiles, see Stored credential transactions .
|
Field Name |
Maximum Length |
Comments |
Required? |
|---|---|---|---|
|
field_agreementSupportedBrands |
- |
A comma-separated list of stored credential transaction frameworks that the customer consent agreement applies to. For example, |
Yes |
|
field_mitConsentAgreementRef |
128 |
Your reference for the stored credential consent agreement that you have established with the customer |
Yes |
|
field_mitConsentAgreementSrc |
- |
Set this field to |
Yes |
|
field_mitCredentialProfileType |
- |
Set this field to |
Yes |
If you perform CITs outside Zuora, include the following fields in the Payment Page 2.0 form after the authentication and authorization are completed. Zuora will then skip the validation for the created credit card payment method. A typical scenario to include these fields in requests is the 3D Secure session.
|
Field Name |
Maximum Length |
Comments |
Required? |
|---|---|---|---|
|
field_agreementSupportedBrands |
- |
A comma-separated list of stored credential transaction frameworks that the customer consent agreement applies to. For example, |
Yes |
|
field_mitConsentAgreementRef |
128 |
Your reference for the stored credential consent agreement that you have established with the customer |
Yes |
|
field_mitConsentAgreementSrc |
- |
Set this field to |
Yes |
|
field_mitCredentialProfileType |
- |
Set this field to |
Yes |
|
field_mitProfileAction |
- |
Set this field to |
Yes |
|
field_mitNetworkTransactionId |
128 |
The networkTransactionId that you get from the payment gateway. |
Yes |
|
field_mitGatewayToken1 |
128 |
The first token if the gateway provides. |
No |
|
field_mitGatewayToken2 |
128 |
The second token if the gateway provides. |
No |
|
field_mitGatewayToken3 |
128 |
The third token if the gateway provides. |
No |