You can configure Secure Payment Profiles settings before creating them.
Must know:
- You must have the Secure Payment Profile feature enabled on your account.
- You will need Full Access to Payment Profiles within the Portal.
How do I configure my Secure Payment Profiles?
- In the Portal, go to Configuration > Payment Profile Configuration.
- Go through the settings below.
General Settings
Setting |
What does it do? |
Does it apply to the Portal or the Payment Profiles API? |
Process all payment profile transactions as recurring payments |
Check this box if all your payment profile transactions are recurring. |
Portal only |
Require unique order numbers |
Please leave this setting unchecked. |
Payment Profiles API only |
Do not allow profile to be created with billing information duplicated from an existing profile |
Check this box if you don’t want to create payment profiles with matching billing address information. |
Portal & Payment Profiles API |
Default to payment profile reference fields for transactions through Process Transaction API |
By default, there are five reference fields associated with a payment profile. If you check this box, the transaction data for profiles will include the data stored in the profile’s ref1 to ref5 fields (as long as the ref1 to ref5 fields are empty in the transaction request through the Payments API). |
Payment Profiles API only |
Security Settings
Setting |
What does it do? |
Does it apply to the Portal or the Payment Profiles API? |
API access passcode |
If you use the Payment Profile API to create payment profiles, generate an API passcode in this field to authorize the profile API requests. |
Payment Profiles API only |
Hash validation is required for all Payment Profile API operation requests |
This setting has been deprecated. Please disregard it and leave unchecked. |
N/A |
Credit Card Settings
Setting |
What does it do? |
Does it apply to the Portal or the Payment Profiles API? |
Require card validation |
Check this box to initiate a $0.00 or $0.50 pre-authorization transaction for any profile you create. This pre-authorization validates a credit card because the payment data is sent to the card-issuing bank to authorize and is recommended. |
Portal & Payment Profile API |
Do not allow profile to be created with card data duplicated from an existing profile |
Check this box if you don’t want to create a payment profile with credit card information that already exists on another profile. |
Portal & Payment Profile API |
Maximum number of cards shown |
Choose from the drop-down to select the maximum number of credit cards that can be stored on a profile. |
Portal & Payment Profile API |
Custom Field Labels
You can customize the labelling of the Ref 1 to Ref 5 data fields. These custom labels may contain up to 255 alphanumeric characters each. (Please disregard Account Reference and Profile Group as they are both deprecated features).
Good to know:
- Please disregard the ‘Velocity Groups’, ‘Profile Groups’, and ‘Credit Card Expiration Email Notification’ sections, as they are deprecated features.
- To learn more about the Payment Profile API passcode (from ‘Security Settings), please see How do I find/update my Payment Profile API passcode?.