Rails Engine

Overview

Mount Rails-native routes, controllers, configuration, and install generators on top of the MakePay Ruby gem.

• Runtime: Ruby on Rails
• Package: makepay-rails
• Mountable Rails engine
• Install generator
• Webhook controller

Installation

gem "makepay-rails"

If the package registry entry is not published in your environment yet, pin the source repository to a reviewed commit and follow the repository README until the package release is available.

Authentication

Create a MakePay API key in MakeCrypto and store the key ID and secret outside source control.

Keep MakePay API keys in trusted server code, worker secrets, or private environment variables.

See API authentication for header names, rotation, and permissions.

Create payment link

Use the SDK or source client to call the MakePay payment links API with an amount, currency, label, customer context, return URL, and metadata. Persist the MakePay payment UID beside your internal order or invoice ID.

The request and response model is documented in payment links.

Webhook verification

Read the exact raw request body, verify the MakePay signature, reject stale timestamps, and process events idempotently.

The signing model and event payloads are documented in webhooks.

Framework notes

• Mountable Rails engine
• Install generator
• Webhook controller
• Keep request creation, webhook verification, and fulfillment updates in trusted backend code.

Source and releases

Review the repository README, examples, and release notes before using the package in production.

Source repository: github.com/makepay-io/makepay-rails

Troubleshooting

• Authentication failures usually mean the key ID and secret belong to different environments or were copied after rotation.
• Webhook failures usually mean the handler parsed JSON before signature verification or the configured webhook secret does not match.
• Checkout issues usually mean the backend did not persist the MakePay payment UID or returned an expired checkout URL.