Vault-as-Payment Source

Paydock's vault allows you to create payment sources on the Paydock side, without any relation to a gateway being used through Paydock. This makes it easier for you to use this token with different payment providers, either now or in future, should you decide to change gateway providers.

Paydock has now added the ability to create payment sources without any relation to a particular gateway. This enables you to create a vault-token payment source on the Paydock side only. 

As you will not pass a gateway_id when creating a payment source, the customer will not be created at the gateway. These new changes have an impact on our Charges, Customers and Subscriptions.

All available functions are presented below.

Customer

When you create a Customer using your Dashboard, it must be associated with a payment source, and therefore your customer will be tokenised directly with that gateway, as described here. However, when creating a new Customer using the Paydock API, if you omit the gateway_id parameter, this Customer will be created only in Paydock's vault, allowing you to use this token across multiple gateways. No other aspects of this new Customer will be impacted and you can choose later to associate it with a gateway_id.

Charge

Our vault-token payment source makes it easy to create charges from the customer side only. By making a charge with a default customer’s payment source, you can specify any of the connected gateways without being tied to a particular gateway. You are also able to use the same customer billing details against multiple payment service providers. 

More information on how to create charges can be found using this link.

Subscriptions

You can also create Subscriptions using a customer with a vault payment source. Just like with Charges from a Customer, you are able to create a Subscription with any gateway.

To find out how to add a subscription, please click here.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us