![]() To collect billing information for the payment option, we can include that option in our plugin definition: * requires_billing_information = TRUE, Though in contrast to the "Manual" payment gateway plugin provided by the Commerce Payment module, our custom plugin will do nothing. It has no payment instructions, never creates a payment, etc. So we can use the "Manual" payment gateway plugin as a model and implement a custom payment gateway plugin that implements the ManualPaymentGatewayInterface interface. Of those options, the processing for ManualPaymentGatewayInterface is the simplest: create a payment and redirect to the next checkout step. The plugin must implement one of these interfaces: The selected "payment option" is processed based on the payment gateway plugin type for the selected payment option. See Drupal\commerce_payment\Plugin\Commerce\CheckoutPane\PaymentProcess::buildPaneForm ( in Drupal Commerce Payment module.) ![]() The "Payment process" checkout pane is the key to understanding how we can create a payment method "Purchase order" option that meets our requirements. A Solution "Purchase order" payment method option For more extensive functionality, you might want to consider the Commerce Purchase Order module.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |