The SDK allows you to implement plugins that interact with payment gateways (processing centers) to handle one-time and recurring payments.
-
For one-time payments, the following Billing payment method types are used:
-
Payment methods of the External Payment Site type. When paying with the method of this type, a customer is redirected from UX1 for Customers to a payment gateway page and uses a payment option supported by the gateway to pay, and is then redirected back to the provider's website. Payment methods of this type in Billing have the .Redirect suffix (for example,
PayPalExpressCheckout.Redirect). -
Payment methods of the Modal Form type. When paying with the method of this type, a customer uses a pop-up window that is embedded into the provider website page, that is, a modal form. Such forms may be supplied by payment system vendors. Payment methods of this type in Billing have the .Modal suffix (for example,
Stripe.Modal).
Using payment methods of these types does not allow the provider to charge subsequent recurring fees without the customer's explicit authorization.
-
-
For recurring payments, the payment methods of the Custom type are used. During a customer's first purchase as described above, the gateway (if supported) returns a token to the provider. Billing stores this token, and the provider is able to charge recurring fees to the same payment method of the customer. Payment methods of this type in Billing have the .Token suffix (for example,
PayPalExpressCheckout.Token).The custom payment methods must be enabled in the system (Provider Control Panel > Billing > Settings > Payment Processing > Manage Payment Methods) and configured prior to the customer's first purchase.
Note: Currently, the SDK does not support bank transfer payment methods (where a user provides their bank account details to a provider).