Payment gateway configuration in Wordpress - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a new payment gateway class in WooCommerce.

Wordpress

add_filter('woocommerce_payment_gateways', '[1]');

Drag options to blanks, or click blank then click option'

Amy_gateway_class

Badd_my_gateway

Cregister_gateway

Dpayment_gateway_hook

Attempts:

3 left

💡 Hint

Common Mistakes

Using the gateway class name directly instead of the function name.

Forgetting to return the gateways array inside the function.

The 'woocommerce_payment_gateways' filter requires a function name that adds your gateway class to the list.

2fill in blank

medium

Complete the code to define the payment gateway class extending WooCommerce's base class.

Wordpress

class WC_[1] extends WC_Payment_Gateway {

Drag options to blanks, or click blank then click option'

AMyGateway

BPaymentBase

CGatewayBase

DPaymentGateway

Attempts:

3 left

💡 Hint

Common Mistakes

Not extending WC_Payment_Gateway.

Using a generic class name that conflicts with others.

Your custom gateway class should extend WC_Payment_Gateway and have a unique name.

3fill in blank

hard

Fix the error in the constructor to initialize the gateway ID correctly.

Wordpress

public function __construct() {
    $this->id = '[1]';
}

Drag options to blanks, or click blank then click option'

AMyGateway

Bgateway_id

Cpayment_gateway

Dmy_gateway

Attempts:

3 left

💡 Hint

Common Mistakes

Using uppercase or spaces in the ID.

Using a generic or reserved ID.

The gateway ID should be lowercase and unique, usually matching your gateway slug.

4fill in blank

hard

Fill both blanks to add your gateway class to WooCommerce and initialize it.

Wordpress

function [1]($gateways) {
    $gateways[] = '[2]';
    return $gateways;
}

Drag options to blanks, or click blank then click option'

Aadd_my_gateway

BWC_MyGateway

Cregister_gateway

DMyGateway

Attempts:

3 left

💡 Hint

Common Mistakes

Using the class name as the function name.

Adding the wrong string to the gateways array.

The function name adds the gateway class name string to the gateways array.

5fill in blank

hard

Fill all three blanks to hook your gateway registration function and initialize the gateway.

Wordpress

add_filter('woocommerce_payment_gateways', '[1]');

add_action('plugins_loaded', function() {
    [2] = new [3]();
});

Drag options to blanks, or click blank then click option'

Aadd_my_gateway

B$gateway

CWC_MyGateway

Dregister_gateway

Attempts:

3 left

💡 Hint

Common Mistakes

Not hooking the function correctly.

Forgetting to instantiate the gateway class.

You hook your function to the filter, then create an instance of your gateway class.

Practice

1. What is the main purpose of configuring a payment gateway in a WordPress site?

easy

A. To allow customers to make payments securely on the website

B. To change the website's theme colors

C. To add new blog posts automatically

D. To improve website loading speed

Solution

1. Step 1: Understand what a payment gateway does

   A payment gateway connects the website to payment services to process payments.

2. Step 2: Identify the correct purpose in the options

   Only To allow customers to make payments securely on the website mentions secure payments, which matches the gateway's role.

3. Final Answer:

   To allow customers to make payments securely on the website -> Option A

4. Quick Check:

   Payment gateway = secure payments [OK]

Hint: Payment gateways handle payments, not design or content [OK]

Common Mistakes:

• Confusing payment gateway with website design features
• Thinking it manages blog posts
• Assuming it speeds up the site

2. Which code snippet correctly adds a new payment gateway class in WooCommerce for WordPress?

easy

A. add_filter('woocommerce_payment_gateways', 'add_my_gateway'); function add_my_gateway($gateways) { $gateways[] = 'WC_Gateway_MyGateway'; return $gateways; }

B. add_action('woocommerce_payment_gateways', 'add_my_gateway'); function add_my_gateway() { return 'WC_Gateway_MyGateway'; }

C. add_filter('woocommerce_payment_gateways', 'add_my_gateway'); function add_my_gateway() { return 'WC_Gateway_MyGateway'; }

D. add_action('woocommerce_payment_gateways', 'add_my_gateway'); function add_my_gateway($gateways) { $gateways[] = 'WC_Gateway_MyGateway'; }

Solution

1. Step 1: Identify correct WordPress hook type

   To modify gateways list, use add_filter, not add_action.

2. Step 2: Check function signature and return

   The function must accept $gateways array, add new gateway, and return the updated array.

3. Final Answer:

   add_filter with function adding to $gateways and returning it -> Option A

4. Quick Check:

   Filter modifies list and returns it [OK]

Hint: Use add_filter with $gateways parameter and return updated array [OK]

Common Mistakes:

• Using add_action instead of add_filter
• Not returning the updated gateways array
• Missing $gateways parameter in function

3. Given this code snippet in a WordPress plugin for WooCommerce payment gateway registration:

add_filter('woocommerce_payment_gateways', function($gateways) {
  $gateways[] = 'WC_Gateway_Custom';
  return $gateways;
});

What will happen after this code runs?

medium

A. Nothing changes because add_filter is used incorrectly

B. The payment gateways list will be replaced with only 'WC_Gateway_Custom'

C. An error will occur because the function does not return anything

D. The custom payment gateway 'WC_Gateway_Custom' will be added to the available gateways list

Solution

1. Step 1: Understand the add_filter usage

   The anonymous function receives $gateways array, adds a new gateway, and returns the updated array.

2. Step 2: Predict the effect on WooCommerce gateways

   The new gateway 'WC_Gateway_Custom' is appended, so it becomes available alongside existing gateways.

3. Final Answer:

   The custom payment gateway 'WC_Gateway_Custom' will be added to the available gateways list -> Option D

4. Quick Check:

   Appending gateway and returning list adds it [OK]

Hint: Returning updated gateways array adds new gateway [OK]

Common Mistakes:

• Thinking the list is replaced instead of appended
• Assuming no return means error
• Confusing add_filter with add_action

4. You wrote this code to add a payment gateway but it causes a fatal error:

add_filter('woocommerce_payment_gateways', 'add_gateway');
function add_gateway() {
  $gateways[] = 'WC_Gateway_New';
  return $gateways;
}

What is the main problem?

medium

A. The function should use add_action instead of add_filter

B. The function add_gateway does not accept the $gateways parameter

C. The gateway class name is incorrect

D. The function does not return anything

Solution

1. Step 1: Check function parameters for filter hook

   Filter functions must accept the value they modify, here $gateways array.

2. Step 2: Identify missing parameter causing error

   Function add_gateway() has no parameters, so $gateways is undefined inside, causing error.

3. Final Answer:

   The function add_gateway does not accept the $gateways parameter -> Option B

4. Quick Check:

   Filter function needs $gateways parameter [OK]

Hint: Filter functions must accept and return the filtered value [OK]

Common Mistakes:

• Omitting the parameter in the filter function
• Using add_action instead of add_filter
• Not returning the updated array

5. You want to configure a payment gateway in WooCommerce that only appears for customers from the US. Which approach correctly applies this condition in your gateway class?

hard

A. Use CSS to hide the payment option on the checkout page for non-US customers

B. Add a filter to remove the gateway from the list after checkout is complete

C. Override the is_available() method in your gateway class to check the customer's billing country and return true only if it is 'US'

D. Set the gateway to be enabled only in the WooCommerce settings without any code

Solution

1. Step 1: Understand how to conditionally show gateways

   WooCommerce gateways can override the is_available() method to control when they appear.

2. Step 2: Apply country check in is_available()

   Checking the customer's billing country inside is_available() and returning true only for 'US' ensures correct display.

3. Final Answer:

   Override is_available() to check billing country and return true only for 'US' -> Option C

4. Quick Check:

   Use is_available() for conditional gateway display [OK]

Hint: Use is_available() method to control gateway visibility by condition [OK]

Common Mistakes:

• Trying to hide gateway with CSS (not secure or reliable)
• Filtering gateways after checkout (too late)
• Only enabling gateway in settings without conditions