​

Complete Guide to Creating and Managing Payment Links

​

Table of Contents

1. What Are Payment Links?
2. Getting Started
3. Creating Your First Payment Link
4. Sharing and Using Payment Links
5. Managing Payment Links
6. API Integration
7. Best Practices
8. Common Use Cases
9. Troubleshooting

​

What Are Payment Links?

• No technical setup required
• Works with any customer, anywhere
• Multiple payment types supported
• Real-time tracking and management
• Customizable for your brand

​

Getting Started

• Access to your payment platform dashboard
• Your business information ready
• Any images you want to use (optional but recommended)
• Clear understanding of what you’re charging for

​

Creating Your First Payment Link

​

Method 1: Using the Dashboard

​

Step 1: Upload an Image (Optional but Recommended)

• Purpose: This image appears when customers view your payment link
• Requirements:
  • Format: JPG or PNG
  • Size: 1024×512 pixels
  • File size: Under 1MB
• How to: Click “Choose File” and select your image
• Best Practice: Use your business logo or product image for brand recognition

​

Step 2: Name Your Payment Link

• Field: “Name of payment link”
• Purpose: This serves as both an internal reference and the title customers see
• Examples:
  • “Monthly Premium Subscription”
  • “Product Purchase - Widget Pro”
  • “Consultation Service Fee”
• Tip: Use clear, descriptive names that customers will immediately recognize

​

Step 3: Add a Description (Optional but Helpful)

• Purpose: Provides additional context about what the customer is paying for
• Best Practice: Include specific details about the product or service
• Examples:
  • “Monthly subscription for premium features including advanced analytics and priority support”
  • “One-time setup fee for new account configuration”
  • “Consultation fee for 60-minute business strategy session”

​

Step 4: Select Your Payment Link Type

​

Step 5: Configure Subaccount (If Applicable)

• Purpose: Route payments to specific business accounts or departments
• How to: Select from the dropdown menu
• Note: This option only appears if you have multiple subaccounts configured
• Use Case: Separate payments for different product lines or business units

​

Step 6: Add Additional Fields

1. Click ”+ Add New Field”
2. Select field type from dropdown:
   • Input: Text, email, number, phone, etc.
   • Select: Dropdown with multiple options
   • Checkbox: Yes/no or agreement fields

• Name: Internal identifier (e.g., “customer_name”)
• Label: What customers see (e.g., “Full Name”)
• Placeholder: Hint text inside the field (e.g., “Enter your full name”)
• Description: Additional help text for customers
• Required: Check if field is mandatory
• Click “Save” to add the field

• Customer Information: Full name, email, phone number
• Shipping Details: Delivery address, preferred delivery time
• Service Preferences: Meeting type, consultation topic
• Custom Requirements: Special instructions, color preferences

​

Step 7: Set Payment Responsibility

• You absorb the processing fees
• Customer pays exactly the displayed amount
• Best for: Transparent pricing, customer-friendly experience
• Example: Product costs ₦1,000, customer pays ₦1,000, you receive ~₦970 after fees

• Customer pays processing fees on top of the amount
• You receive the full displayed amount
• Best for: When you need to receive exactly the stated amount
• Example: Product costs ₦1,000, customer pays ₦1,030, you receive ₦1,000

​

Step 8: Configure Link Reusability

• Link can be used multiple times
• Best for: Products, subscriptions, ongoing services
• Example: Monthly subscription link used by the same customer each month

• Link becomes invalid after first successful payment
• Best for: Invoices, single purchases, limited offers
• Example: Specific invoice for a particular customer

​

Step 9: Set Additional Options

• Purpose: Receive real-time payment notifications on your server
• Format: https://yoursite.com/webhook/payment
• Use Case: Automatically update your records when payments are received

• Purpose: Where to redirect customers after successful payment
• Format: https://yoursite.com/thank-you
• Use Case: Show confirmation page, provide download links, or display next steps

• Purpose: Personalize your payment link URL for branding
• Base URL: https://pay.monieswitch.com
• Example: https://pay.monieswitch.com/your-business-subscription
• Best Practice: Use descriptive, memorable URLs

​

Method 2: Using the API

curl --location 'https://nini.monieswitch.com/payment-link' \
--header 'Authorization: Bearer {{merchantAPIKey}}' \
--data-raw '{
    "amount": 200,
    "channel": "API",
    "name": "Product Purchase",
    "description": "One-time setup fee",
    "supportCard": true,
    "requiresName": true,
    "requiresPhone": true,
    "supportBankTransfer": true,
    "webhookURL": "https://yoursite.com/webhook/payment",
    "callbackURL": "https://yoursite.com/thank-you",
    "email":"[email protected]",
    "fields": [
      {"type": "text", "name": "customer_name", "label": "Full Name"},
      {"type": "tel", "name": "phone", "label": "Phone Number"}
    ],
    "chargeBearer": "merchant",
    "reusable": true,
    "customLink": "your-custom-link"
}'

​

Sharing and Using Payment Links

​

How to Share Your Payment Link

• Copy the link and send via email
• Share on social media platforms
• Include in SMS messages
• Add to messaging apps (WhatsApp, Telegram, etc.)

<form action="{paymentLink}" method="post">
  <button type="submit">Pay Now</button>
</form>

• Generate QR codes for in-person payments
• Include in printed materials
• Display at physical locations

​

Customer Experience

1. See your uploaded image (if provided)
2. Read the payment name and description
3. Enter payment amount (if applicable)
4. Fill out additional fields (if required)
5. Choose payment method
6. Complete the payment
7. Get redirected to callback URL (if configured)

​

Managing Payment Links

​

Dashboard Management

• Access all payment links from your dashboard
• View status (active/inactive)
• See total payments received
• Check recent transaction activity

1. Deactivate/Reactivate: Control when links can accept payments
2. Edit Details: Update name, description, or additional fields
3. View Transactions: See all payments made through the link
4. Test Payment: Make a test transaction to verify functionality
5. Copy Link: Quickly copy the payment URL

​

API Management

curl --location --request DELETE 'https://nini.monieswitch.com/payment-link?paymentLinkID={ID}' \
--header 'Authorization: Bearer {{merchantAPIKey}}' \
--data ''

curl --location --request PATCH 'https://nini.monieswitch.com/payment-link/activate' \
--header 'Authorization: Bearer {{merchantAPIKey}}' \
--data '{
    "paymentLinkID": "{ID}"
}'

​

Best Practices

​

For Better Conversion Rates

• Use descriptive names that immediately convey value
• Write helpful descriptions that eliminate confusion
• Include relevant images to build trust and recognition

• Choose the right link type for your business model
• Set reasonable additional field requirements
• Configure callback URLs for better customer experience

​

For Better Management

• Use consistent naming conventions across all links
• Group similar payment links logically
• Regular review and cleanup of unused links

• Set up webhooks for automatic payment tracking
• Integrate with your existing business systems
• Use API for bulk operations when needed

• Test all links thoroughly before sharing with customers
• Verify webhook notifications work correctly
• Check callback URL redirection

​

Security Considerations

• Always use HTTPS URLs for webhooks and callbacks
• Validate webhook signatures on your server
• Monitor for suspicious payment activity

• Don’t include sensitive information in link names or descriptions
• Regularly audit access to payment link management
• Use appropriate field validation for customer data

​

Common Use Cases

​

E-commerce Business

• Type: Fixed Amount or Dropdown Selection
• Additional Fields: Customer name, shipping address, product preferences
• Callback URL: Order confirmation page with tracking information
• Example: Online store selling products with different variants

​

Service-Based Business

• Type: Fixed Amount or Input Amount
• Additional Fields: Project details, contact information, service requirements
• Webhook: Update project management system automatically
• Example: Consulting firm charging for different types of services

​

Non-Profit Organization

• Type: Custom Amount
• Additional Fields: Donor name, message, tax receipt preference
• Callback URL: Thank you page with donation receipt
• Example: Charity accepting donations of any amount

​

Subscription Services

• Type: Fixed Amount
• Reusability: Reusable
• Additional Fields: Account email, subscription preferences
• Webhook: Update customer account status
• Example: SaaS platform with monthly billing

​

Event Management

• Type: Dropdown Selection (different ticket types)
• Additional Fields: Attendee information, dietary restrictions, t-shirt size
• Callback URL: Ticket confirmation page
• Example: Conference with multiple ticket tiers

​

Troubleshooting

​

Common Issues and Solutions

• Problem: Uploaded image doesn’t appear on payment page
• Solutions:
  • Check file size is under 1MB
  • Ensure format is JPG or PNG
  • Verify image dimensions (recommended: 1024×512 pixels)
  • Try uploading a different image

• Problem: Customers can’t access the payment page
• Solutions:
  • Verify all required fields are completed
  • Check if link is still active (not deactivated)
  • Ensure payment amount is properly configured
  • Test link in different browsers

• Problem: Not receiving payment notifications
• Solutions:
  • Ensure webhook URL is publicly accessible
  • Verify URL returns HTTP 200 status code
  • Check server logs for incoming requests
  • Test webhook URL independently

• Problem: High abandonment rate or customer support questions
• Solutions:
  • Add clearer descriptions explaining the payment
  • Include relevant additional fields for context
  • Use appropriate images to clarify what’s being paid for
  • Test the customer experience yourself

• Problem: API calls failing or returning errors
• Solutions:
  • Verify API key is correct and active
  • Check request format matches documentation exactly
  • Ensure all required fields are included
  • Review API response for specific error messages

​

Testing Your Payment Link

1. Create a Test Link:
   • Set up with a small amount (e.g., ₦10)
   • Include all features you plan to use
   • Use test mode if available
2. Complete Test Transaction:
   • Go through entire payment process
   • Fill out all additional fields
   • Use different payment methods
3. Verify Integration:
   • Check webhook notifications arrive correctly
   • Confirm callback URL redirection works
   • Verify additional field data is captured
4. Check Customer Experience:
   • Test on different devices (mobile, desktop)
   • Try different browsers
   • Verify loading speeds
5. Monitor and Adjust:
   • Review transaction details in dashboard
   • Make necessary adjustments based on test results
   • Re-test after any changes

​

Final Steps and Launch

​

Pre-Launch Checklist

• All payment information is accurate
• Images display correctly
• Additional fields work as expected
• Webhook notifications are received (if configured)
• Callback URL redirects properly (if configured)
• Test transaction completed successfully
• Customer experience tested on multiple devices
• Security measures are in place

​

Going Live

1. Start Small: Share with a limited group first
2. Monitor Closely: Watch for any issues in the first few transactions
3. Gather Feedback: Ask early customers about their experience
4. Iterate: Make improvements based on real usage data
5. Scale Up: Gradually increase sharing as you gain confidence

​

Ongoing Management

• Monthly check of payment link performance
• Quarterly review of additional fields effectiveness
• Annual audit of all active links

• A/B test different descriptions or images
• Analyze conversion rates by traffic source
• Optimize additional fields based on completion rates

• Update webhook URLs when needed
• Refresh images periodically
• Archive unused payment links

​

Conclusion