Accept payments in-app
Charge cards, ACH and tokenized payments without leaving your app.
PayJunction Connector
Embed PayJunction payment acceptance and reconciliation into your product. Build in-app flows to create charges, vault tokens, issue refunds and surface transaction events for customers using Cyclr’s low-code orchestration and white-label marketplace.
Manage payment data
Create customers, save tokens and sync vault records.
Reduce PCI scope
Use tokenization and hosted flows to limit card data exposure.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Integrate PayJunction to accept in-app payments, vault card tokens, issue refunds, manage customers and terminals, and subscribe to transaction webhooks. Use Cyclr’s low-code builder to compose payment workflows, handle tokenization, and publish integrations into your embedded marketplace. See PayJunction API documentation for endpoints and keys. (developer.payjunction.com)
PRODUCT USE CASES
Top Use Cases for PayJunction Integrations
Quickly add in-app charge flows, tokenization, refunds and webhook-driven order or billing automation. Publish your PayJunction integration into your product via Cyclr’s white-label embedded marketplace.
In-app charge flows
Create charges using POST /transactions to accept card or ACH payments and return transaction status into your application records.
Card tokenization and re-billing
Save tokenized cards to the Vault and re-bill customers later using tokenId or schedule IDs for recurring payments.
Sync customers and terminals
Mirror PayJunction customers, terminal and merchant records into your app for reconciliation, reporting and multi-location routing.
ORCHESTRATION
How PayJunction works with Cyclr
Cyclr sits between your SaaS product and PayJunction to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
PayJunction
PayJunction processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore PayJunction methods you can orchestrate through Cyclr.
Transactions2
Transaction Webhook
WebhookGet details of a transaction immediately after it has been processed.
Get Transaction
ActionGet a transaction.
Deposits3
Get Deposit
ActionGet a deposit.
List Deposits
ActionList all deposits.
List New Deposits
ActionList all new deposits.
Customers4
List New Customers
ActionList all new customers.
List Customers
ActionList all customers.
Get Customer
ActionGet a customer.
List Updated Customers
ActionList all updated customers.
TECHNICAL DETAILS
PayJunction integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing PayJunction integrations in Cyclr.
API and authentication
- API host
https://api.payjunction.com- Authentication
- Application key; HTTP Basic Auth
- Credentials
X-PJ-Application-Key; API username; API password; Environment/base URL (sandbox or production).
- Method categories
Transactions; Refunds; Customers; Terminals; Vaults/tokenization; Schedules; Webhooks
Pagination and rate limits
Pagination
Offset/limit pagination. Responses include next and prev URLs. Use offset and limit query parameters; limit maximum is 50. (developer.payjunction.com)
Rate limits
Default rate limit is one request every 100 milliseconds; avoid rapid duplicate requests or auth retries. (developer.payjunction.com)
IMPLEMENTATION
Authentication at a glance
PayJunction requires an X-PJ-Application-Key header plus an API login and password sent via HTTP Basic. Cyclr connector captures application key, username, password and environment selection during setup. (community.cyclr.com)
- Authentication method
- Application key; HTTP Basic Auth
- Credential required
X-PJ-Application-Key; API username; API password; Environment/base URL (sandbox or production).
Before you begin:
View setup guideRequest an Application Key and create an API user in PayJunction before installing.
COMMON QUESTIONS
Frequently asked questions
It accepts in-app payments, creates transactions, issues refunds, saves tokenized cards to the Vault, manages customers and terminals, and subscribes to transaction webhooks to trigger downstream workflows.
PayJunction requires an X-PJ-Application-Key plus an API username and password (HTTP Basic). Cyclr asks for the application key, API username, password and environment during connector setup. (developer.payjunction.com)
Yes. Cyclr supports tenant-specific credentials so each customer can use separate PayJunction credentials or PJMIDs; note webhooks and some events are tied to each merchant PJMID and must be subscribed per account. (developer.payjunction.com)
Yes. Platform teams can expose selected PayJunction actions (for example create charge, refund, vault read) as governed MCP tools in Cyclr’s embedded marketplace, subject to Console configuration and method support.
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductTeaming up your POS and eCommerce Integrations
Read more →ProductMCP PaaS
Read more →Related connectorAuthorize.net
Related Billing/Payment connector for customer-facing integration workflows.
Related connectorBookeo
Related Billing/Payment connector for customer-facing integration workflows.
Related connectorCardpointe
Related Billing/Payment connector for customer-facing integration workflows.