The Rapyd Works With Developer Hub

Welcome to the Rapyd Works With developer hub. You'll find comprehensive guides and documentation to help you start working with Rapyd Works With as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Rapyd Payments App for Ecwid

Start accepting payments from your Ecwid store.

With Rapyd, you can quickly accept more payment methods from more countries. Payment methods like ewallets, bank transfers, cards and cash.

Rapyd offers this Ecwid add-on in over 50 countries.

See List of Supported Countries (You must be domiciled here in order to accept payments)

Andorra, Armenia, Austria, Australia, Belgium, Bosnia and Herzegovina, Brazil, Bulgaria, Canada, Chile, Colombia, Croatia, Cyprus, Czech Republic, Denmark, Dominican Republic, El Salvador, Estonia, Finland, France, Georgia, Germany, Gibraltar, Greece, Greenland, Hong Kong, Hungary, Iceland, India, Indonesia, Ireland, Israel, Italy, Japan, Latvia, Liechtenstein, Lithuania, Luxembourg, Macedonia, Malaysia, Malta, Mexico, Moldova, Monaco, Montenegro, Netherlands, New Zealand, Norway, Peru, Philippines, Poland, Portugal, Romania, San Marino, Singapore, Slovakia, Slovenia, South Africa, South Korea, Spain, Sweden, Switzerland, Taiwan, Thailand, Turkey, UK, USA, Vatican, Vietnam, Virgin Islands (USA)

🚧

Rapyd Account Connection Limit

You can only connect one store per Rapyd Account.

Step 1: Get Started with Rapyd Payments

With a Rapyd Client Portal account, you can:

  • Activate and set up your plugin.
  • Access sandbox mode and test payments.
  • View supported payment methods.
  • View payment reports.
  • Invite team members.
  • Complete KYB steps to fully activate your account.

Step 2: Activate the App from the Rapyd Client Portal

A. Sign in to Client Portal and navigate to Plugins. Click Ecwid.
B. On the Ecwid page, click the Active toggle button.
Note: You can search supported countries in the search bar.

1676

Step 3: Add the App from the Ecwid Control Panel

A. In the Ecwid control panel, go to Payment.

1686

B. Scroll down to the Payment Alternatives section, and select Rapyd Payments from the Choose Payment Processor dropdown menu.

860

C. Click on the Add Payment Method button that appears on the pop-up window.

587

πŸ“˜

Apple Pay

European customers with an Apple account may use Apple Pay for purchases when using Safari. See supported countries here.

The Rapyd Payments account details page appears.

1390

Step 4: Configure the Sandbox Mode

πŸ“˜

Note

The Client Portal must be in sandbox mode during this testing phase. See Select Environment.

A. In the Rapyd Payments account details page, click the Enable test mode toggle button.
B. Enter your Rapyd Access Key and Secret Key for the sandbox environment in the Test Access key and Test Secret key fields. Note that you should use the unique production keys for the Ecwid plugin. See also Viewing Plugin Keys.
C. In the Appearance options section, enter a name for the payment method as it will appear in your site’s checkout screen. It is recommended that you provide a name that indicates a test mode.
D. Click on the Enable this payment method at checkout toggle button.

1381

E. Click the Save button.
F. Go to the Cart & Checkout tab in Settings > General, and enable the Ask for a billing address during checkout setting.

1221

πŸ“˜

Note

This billing address setting should also be enabled during production mode.

Step 5: Testing the App

A. Go to your Ecwid ecommerce site as a customer and add an item to the cart.
B. Click on the Go to Checkout button.

1239

C. Enter your email address and click the Checkout button.

1365

D. Select the Rapyd Payments method, enter a billing address, and click on the Go to Payment button.

1209

E. For testing purposes, select any type of payment and fill in the additional fields. For example, enter the following test values for a Mastercard card payment:

  • Card: Mastercard
  • Card number: 4111 1111 1111 1111
  • Expiration Date: 12/23
  • CVV Code: 123
  • Cardholder Name: John Doe

F. Click on the Place Your Order button.

1401

G. Click the Finish button on the Payment Successful screen that appears.

884

A confirmation message appears.

716

H. Go to the My Sales > Orders section of the Ecwid Admin panel and verify that the payment you have made is displayed with the correct status.

1234

After you have finished testing the app, you can switch to production mode.

Step 6: Configure the Production Mode

πŸ“˜

Note

The Client Portal must be in production mode. See Select Environment.

A. In the Ecwid control panel, go to Payment.
B. Click on the Actions button of the Rapyd Payments window and select Edit.

997

The Rapyd Payments account details page appears:

1381

C. Click the Enable test mode toggle button to disable it.
D. Enter your Rapyd Access Key and Secret Key for the production environment in the Access key and Secret key fields. Note that you should use the unique production keys for the Ecwid plugin. See also Viewing Plugin Keys.
E. In the Appearance options section, enter a name for the payment method as it will appear in your site’s checkout screen. It is recommended that you provide a name that indicates a payment method that your customers can use.

1257

F. Click the Save button.
G. To fully activate your account for production mode, you’ll need to complete the KYB form for compliance review in the Rapyd Client Portal.

Step 7: Set up a Landing Page URL

After the checkout process completes, the customer can be forwarded to a landing page. This may be the main URL of the ecommerce site or any other landing page that you may want to define. To set the landing page URL:
A. Sign in to the Client Portal and navigate to Settings > Branding.

1741

B. Click on the link icon and enter the URL of the landing page in the Fallback URL field.

1560

C. Click Save.

πŸ“˜

Note

For more information on customizing your checkout page, see Hosted Checkout Page Integration Steps.

Updated 4 months ago

Rapyd Payments App for Ecwid


Start accepting payments from your Ecwid store.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.