Pay an unpaid invoice
Link a customer to the secure payment page connected to the invoice amount, status, business, and generated PDF.
Website payment integration
Add secure 850 Payments links to a service website.
850 Payments supports service websites through secure payment links created for an invoice, standalone request, or approved recurring contract. The customer opens an 850 Payments page, reviews the business and amount, and continues to Stripe-hosted checkout. Payment-request creation remains authenticated inside 850 Work today; it is not an open public card-processing API.
What is an API?Plain-language explanation
An API is a secure bridge that lets two systems exchange only approved information. For 850 Payments, the business website uses a payment link issued by 850 Work, and Stripe handles the checkout. The website never receives raw card details, secret keys, or private merchant controls.
Website uses
What 850 Payments can add to a business website
Send the link by email
Email Center can attach the existing 850 Work invoice PDF and include or exclude its payment link before sending.
Use a standalone request
Create a payment request for a selected customer or an entered recipient when a normal invoice is not the starting point.
Approve recurring contracts
Send a monthly contract approval link so the customer reviews the amount and consents before recurring Stripe billing begins.
Return to updated records
Verified Stripe events update the linked payment order and can close the connected invoice after the recorded amount is paid.
Keep card entry off the website
The website and 850 Work do not collect raw card numbers or CVV values; Stripe hosts the sensitive checkout step.
Current integration
Use a generated link instead of building a card form
- Connect the business merchant account. The owner completes Stripe onboarding from the authenticated 850 Payments area.
- Create the payment request in 850 Work. Choose the invoice, contract, customer, or recipient and confirm the amount and permitted pricing display.
- Place or send the issued link. Use it in an invoice email, customer message, managed business website, or technician-assisted payment flow.
- Let Stripe collect payment details. The customer confirms the request and enters card information on Stripe-hosted checkout.
- Wait for verified confirmation. 850 Work relies on signed payment events rather than trusting a browser redirect to mark the invoice paid.
Payment fees: payments processed through 850 Payments are subject to Stripe's applicable processing charges plus a disclosed 0.5% 850 Work platform fee. Adding an issued link to a website does not create an additional API fee.
API status
The public website gets a payment path, not private payment controls
850 Work does not currently publish a general-purpose endpoint that lets arbitrary websites create charges, issue refunds, list merchant transactions, or handle card data. Those actions remain behind authenticated business permissions and the payment service. This narrower design keeps Stripe credentials, connected-account controls, customer financial records, refunds, disputes, and webhook processing off public website code.
- Available now: secure generated invoice, standalone, and recurring-contract approval links.
- Suitable for a website: a Pay invoice button or customer message can open the issued hosted payment page.
- Not suitable for browser code: secret keys, account tokens, raw card fields, refund controls, and transaction exports.
- Managed integrations: contact info@850work.com when a business website needs a reviewed payment-link connection.
Payment security
Keep the invoice context while Stripe handles regulated payment functions
The hosted 850 Payments page can show the contractor's business name, reference, amount, due date, and downloadable invoice before the customer continues to Stripe. Stripe handles card entry, merchant verification, processing, and payouts. 850 Work keeps non-sensitive references and verified status records without holding customer funds.
Direct answers
Frequently asked questions
Can a customer pay from a business website?
Yes. The business can place or send the secure 850 Payments link created for that invoice, standalone request, or approved recurring contract.
Is there a public API that lets a website create any card charge?
No. Payment-request creation and merchant controls remain authenticated inside 850 Work. Public website code should use an issued payment link and must not handle secret keys or raw card data.
Does the customer need an 850 Work login?
No. A customer can open the secure payment link without an employee workspace account.
Can the payment page include the invoice?
Yes. Invoice payment requests retain the exact PDF generated by the 850 Work document renderer so the customer can review or download it.
How does an invoice become paid?
850 Work waits for a verified Stripe event, matches the payment to its order and invoice, and then updates the linked records. A browser return by itself is not treated as payment proof.
Keep exploring
Related 850 Work pages
Try 850 Work with sample data first.
The demo does not require a credit card. Full access is managed from inside the app.