Skip to main content

​
Overview

Payment Requests let you collect money fast in two ways:
  • Links: Generate a pay link and share it anywhere.
  • Push (Bank Push): Trigger a payment request straight to the customer’s banking app (currently Capitec Bank only).
No heavy integration, no complex checkout—just a simple path to getting paid.

​
Types of Payment Requests

Push (Bank Push) is in Beta and currently supports Capitec Bank only. More banks coming soon.

​
Key Features

  • No Partial Payments: Simplifies reconciliation by allowing only full payments.
  • Multi-Channel Sharing (Links): Send via SMS, WhatsApp, email, or social.
  • Real-Time Tracking: Monitor status in the dashboard or via webhooks.
  • Secure Checkout: PCI DSS, OTPs, 3D Secure, and fraud controls.
  • Multiple Payment Methods (Links): Cards, mobile money, bank transfers, and more.
  • Fast Onboarding: Get started in minutes.
  • No-Code Friendly (Links): Create and manage links from the dashboard (coming soon).
  • Boost Cash Flow: Reminders, expiries, and smart retries.
  • High Conversion: Optimized UX on a reliable, fast platform.
  • Effortlessly Scalable: Works for 10 or 10,000+ requests.
  • Low Friction (Push): No card entry; customer approves in their bank app.
  • Lower Fraud Risk (Push): Bank-authenticated approval flow.

​
Common Use Cases

Need help deciding between Links and Push? Use Links for broad reach and instant sharing. Use Push when your customer is on a call/chat and can approve directly in their banking app (Capitec).

​
How It Works

  1. Create a payment request (dashboard or API).
  2. Share the unique URL via WhatsApp, SMS, email, or social.
  3. Customer opens the secure checkout.
  4. Customer pays with their preferred method.
  5. You receive real-time status updates.

​
B. Push (Bank Push – Capitec)

  1. Create a push payment request via API (include customer identifier).
  2. The customer receives a payment prompt in their Capitec app.
  3. The customer reviews and approves the request.
  4. Status updates flow to your system via API/webhooks.
For Push, the customer must have an active and reachable Capitec banking app. The authorization window may be time-limited.

​
Ways to Create Payment Requests

Moment supports both no-code and developer options.

​
1) Dashboard (No-Code) COMING SOON

Ideal for: Teams wanting a manual, no-code flow. Steps:
  1. Log in to the dashboard
  2. Open Payment Requests
  3. Click Create Payment Request
  4. Enter amount, currency, description, expiry (optional)
  5. Generate & copy the link
  6. Share it with your customer
Push (Bank Push) creation from dashboard is planned for a future release.

​
2) API Integration

Ideal for: Automating flows from CRMs, ERPs, or order systems.
  • Create: POST /collect/payment_requests with type link, this returns a unique link_url which can be forwarded for payment.
  • Retrieve: GET /collect/payment_requests/:id
  • Webhook events: Created, Paid & Updated.

​
Push (Capitec)

  • Create: POST /collect/payment_requests with type push, this should send a push notification to the banking app.
  • Retrieve: GET /collect/payment_requests/:id
  • Webhook events: Created, Paid & Updated.

​
Status Lifecycles

​
Customization Options

Links support:
  • Logo/Branding
  • Payment description
  • Link expiry
  • External Reference (tags or internal references)
  • Metadata
Push uses the bank’s UI for approval. You can still pass:
  • Description / Reference (shown to the customer in-app where supported)
  • External Reference & Metadata (for your internal reconciliation)

​
Getting Started

  1. Sign up as a Moment merchant
  2. Choose Links or Push for your use case
  3. Create the request
  4. Share the link or let the bank app prompt the customer (Push)
  5. Track status via API and Webhooks

​
Webhooks

Moment sends webhook events to your registered endpoint as a payment request moves through its lifecycle. Use these to trigger downstream workflows, send confirmations, or update internal records. See Webhook Setup to register your endpoint and Webhook Verification to validate incoming events.

​
Next Steps