Enter only the fields the provider requires
Store ID, optional merchant ID, write-only auth key, optional API key and Live/Test mode.
- Selected business profile
- Explicit live or test mode
- Write-only secret editing
Payment integration
Connect Telr without treating checkout as proof
Use Telr one-time invoice checkout in Invoice Crowd with authenticated order checks and exact paid-state verification.
- Status: Active one-time checkout
- Verified against application docs
- Provider terms still apply
Last updated:
Configuration to settlement
How Telr fits the Invoice Crowd payment boundary
Connection, customer checkout and final settlement are separate stages. Read the status and limitations before showing the method on a live invoice.
Connect the merchant account
Credentials and mode stay tied to the selected business.
Confirm provider eligibility before rollout
Telr controls merchant markets, currencies, account services and fees.
- Merchant country and account
- Invoice and settlement currency
- Provider fees and review
Understand the customer path
Availability is evaluated before a customer enters checkout.
Use the supported one-time flow
The active flow uses Telr's order create/check contract and accepts only exact paid code 3 with authorized sale or e-commerce transaction proof.
- Server-owned amount
- Bound invoice allocation
- Provider-controlled payment step
Read the recurring-payment boundary separately
Telr subscription renewal and cancellation are retired until separate credentials and immutable agreement mappings exist.
- One-time and recurring differ
- Existing bindings may be compatibility-only
- Retired creators stay unavailable
Verify before recording money
The final local state follows provider evidence, not the browser.
Match the commercial record exactly
Authenticated order check, exact order reference, merchant/account, allocation, amount, currency and paid transaction state.
- Merchant account and mode
- Allocation, amount and currency
- Successful provider state
Keep the current limitation visible
Ambiguous, partial and split legacy references fail closed. The browser return is not the settlement authority.
- No inferred settlement
- Pending stays pending
- Mismatch fails closed
Integration facts
What to verify before using Telr
The fields below describe the current Invoice Crowd path; the provider remains the source for merchant eligibility, fees and regional availability.
-
Availability
Active one-time checkout
-
One-time payment
The active flow uses Telr's order create/check contract and accepts only exact paid code 3 with authorized sale or e-commerce transaction proof.
-
Recurring payments
Telr subscription renewal and cancellation are retired until separate credentials and immutable agreement mappings exist.
-
Merchant setup
Store ID, optional merchant ID, write-only auth key, optional API key and Live/Test mode.
-
Settlement evidence
Authenticated order check, exact order reference, merchant/account, allocation, amount, currency and paid transaction state.
-
Regional fit
Telr controls merchant markets, currencies, account services and fees.
-
Current boundary
Ambiguous, partial and split legacy references fail closed. The browser return is not the settlement authority.
-
Invoice data
Amount, currency and allocation are derived from the current server-side invoice state.
-
Customer result
A provider screen or browser return is a locator, not sufficient settlement proof.
-
Retries
Durable attempts and stable provider identities prevent an uncertain response from becoming an unbounded duplicate payment.
-
Provider fees
Gateway fees, exchange costs and settlement timing come from the merchant agreement, not the Invoice Crowd subscription.
-
Alternative gateways
Configure another active provider when this gateway does not support the merchant, customer, currency or collection model.
Questions
Telr and Invoice Crowd, answered
Is the Telr integration currently available in Invoice Crowd?
Current status: Active one-time checkout. The active flow uses Telr's order create/check contract and accepts only exact paid code 3 with authorized sale or e-commerce transaction proof.
What do I need to connect Telr?
Store ID, optional merchant ID, write-only auth key, optional API key and Live/Test mode. Telr controls merchant markets, currencies, account services and fees.
How does Telr one-time checkout work?
The active flow uses Telr's order create/check contract and accepts only exact paid code 3 with authorized sale or e-commerce transaction proof.
Does Telr support recurring payments in Invoice Crowd?
Telr subscription renewal and cancellation are retired until separate credentials and immutable agreement mappings exist.
How does Invoice Crowd decide that a payment succeeded?
Authenticated order check, exact order reference, merchant/account, allocation, amount, currency and paid transaction state. A browser return or posted status alone cannot settle the invoice.
Are gateway fees included in Invoice Crowd pricing?
No. Provider transaction fees, foreign-exchange costs, settlement timing and account terms are controlled by the gateway and merchant agreement. Check the provider before activation.
Test Telr with a representative invoice
Start with sandbox or test mode where the provider offers it, verify the exact currency and payment result, then plan production activation.
- No browser-only settlement
- Provider terms apply
- Current status is visible