Create payment methods on Global Payments
This payment gateway integration can be requested through the Specialized Payment Connections service at an additional cost.
To create Credit Card payment methods on Global Payments, use one of the following approaches:
REST API approach
You can create tokenized Credit Card payment methods through the Create a payment method API operation. Use one of the following options.
Option 1: Pass in card information and the tokenize flag
You can pass in the card information and a tokenization flag field. A token is generated when validating the payment method with the gateway. Both the card information and the token are stored for the payment method but the token is used in processing subsequent payment transactions.
In your request, pass in the following required fields:
Required Field | Type | Description |
---|---|---|
accountKey |
string |
The Zuora internal ID of the customer account that will own the payment method. While this field is not required when creating an orphan payment method, specifying this field is highly recommended to associate a newly created payment method with an account. |
cardNumber |
string |
The credit card number. |
cardHolderInfo |
object |
Container for cardholder information. The nested |
cardType |
string |
The type of the credit card. |
expirationMonth |
integer |
One or two-digit expiration month (1-12) of the credit card. |
expirationYear |
integer |
Four-digit expiration year of the credit card. |
type |
string |
The type of the payment method. Specify |
tokenize |
boolean |
default: false Specify |
Here is an example of the API request for creating a tokenized Credit Card payment method:
{ "accountKey": "8a90d6128d45df2b018d4b90681c05x0", "cardHolderInfo": { "cardHolderName": "Amy Lawrence" }, "cardNumber": "4111111111111111", "cardType": "Visa", "expirationMonth": "03", "expirationYear": "2050", "securityCode": "733", "type": "CreditCard", "gatewayOptions": { "InvoiceNum": "I11", "RegisterNumber":"s", "cardPresence":"PRESENT" }, "tokenize": true }
For other optional fields, see Create a payment method.
Option 2: Pass in your existing token
You can pass in the existing token you have obtained from transactions outside of Zuora. A Credit Card payment method is created by using the provided token, and the token is used in processing subsequent payment transactions.
In your request, pass in the following required fields:
Required Field | Type | Description |
---|---|---|
accountKey |
string |
The Zuora internal ID of the customer account that will own the payment method. While this field is not required when creating an orphan payment method, specifying this field is highly recommended to associate a newly created payment method with an account. |
cardMaskNumber |
string |
The masked card number. |
cardType |
string |
The type of the credit card. |
tokens |
object |
Pass in your existing token information through the following nested fields in this container:
|
type |
string |
The type of the payment method. Specify |
For other optional fields, see Create a payment method.
Here is an example of the API request:
{ "type": "CreditCard", "cardType": "Visa", "cardMaskNumber": "*******1111", "tokens": { "gatewayType": "GlobalPayments", "tokenId": "10000010AM3T5VJ75UYA" }, "accountKey": "8ac680458ed1c4ba018ed2237bfa416a" }
Hosted payment page approach
You can implement a hosted payment page through the Payment Pages 2.0 solution to collect your customer's payment method data and create the payment method in Zuora. When creating a payment method through the hosted payment page, a token is generated and stored for the payment method.
For more information about the implementation of hosted payment pages, see Payment Pages 2.0 implementation overview.
Zuora UI approach
See Set up the payment method through the Zuora UI for more information. When creating payment methods through the UI, a token is generated and stored for the payment method.
Required configuration settings
For tokenized payment methods, you must validate them in Zuora so that payments made with these payment methods are successful. To validate tokenized payment methods, enable the following settings on the gateway instance configuration page:
- Verify new payment method
- Verify updated payment method