Generic Payment Info Request Links

Generic Payment Info Request links let you send easy to copy URLs that prompt your customer to submit their payment details (card or bank) directly into Benji Pays—even before they exist in your accounting system. You can:

• Embed them on your website or customer portal
• Drop them into any tokenized email template (CRM, marketing automation, help desk)
• Copy & paste them into manual emails

Because they’re parameterized, you can pre-fill your customer’s name, email, phone number, and ensure a seamless onboarding or payment collection flow.

When & Why to Use

• Onboarding New Customers
  Send a link to collect card or ACH info as part of setup, before they’re in QuickBooks, Xero, etc.
• Embedding in CRM/Marketing Emails
  Use HubSpot, Salesforce, Mailchimp tokens so each recipient gets a personalized link.
• Website or Portal Integration
  Add a “Update Your Payment Info” button on your own site pointing to the Generic Request URL.
• Manual Email or Chat
  Quickly request updated payment details—expired card, failed ACH, billing-change—with one click.

How are these different then normal Payment Info Requests sent form Benji Pays?

These links are not connected to a customer in your accounting system when they are sent, you will link them after the customer enters the information.  Also these are used when sending emails generated outside of Benji Pays, which you may need to do depending on your workflows

Finding Your Generic Request Links

1. Log in to Benji Pays.
2. Go to Payment Info Requests.
3. At the top of the page locate the row for the gateway , currency, and payment type you would like to send.
4. Click Copy to grab the base URL.

Tip: Merchants with credit card and bank payments will see more than one link, choose the one that reflects the payment types you'd like your customer to be able to choose from

Supported Query-String Parameters

Help your customers by populating form fields for them. Generic Request Links support the use of query parameters to pre fill certain fields in the form saving your users time and helping to reduce errors.

Pro tips:

• Populate these parameters using your CRM's merge-field syntax—e.g., ?customerEmail={{Contact.Email}}.
• All values should be URL-encoded (e.g. space → %20, @ → %40, [/] → %5B/%5D).  This site can help you encode the values.

Putting It All Together

https://portal.benjipays.com/.../cardrequest?customerName=Acme%20Corp&customerEmail=bob%40acme.com&customerPhone=1-604-888%205555

After Submission

1. Customer Submits Info: They complete the secure form and click “Submit.”
2. Merchant Notification: Your team will receive an email notification telling you a new payment method has been provided.
3. Locate the Request: In the portal, go to Profiles → Payment Info Requests. Each row shows Customer, Gateway, Date Sent, Viewed, Completed, and Actions.
4. Link to Accounting: Once that customer record exists in your accounting system, click the ? Link icon in the Actions column to attach the new card or bank details to the correct customer profile.
5. Confirmation: After linking, the payment method will appear on the customer’s profile in both Benji Pays and your accounting system.

Best Practices

• URL-encode all params if possible.
• Test links first. Paste in browser to verify.