Embedded Terminal
Put your full virtual terminal inside another software product - your team charges cards and checks without ever leaving the program they already work in.
What the embedded terminal is
If your business runs on another software product - a practice manager, an accounting package, a booking system - the embedded terminal puts your complete Merchant360 virtual terminal inside that program. Your staff open the terminal page in the software they already use, and everything works exactly like the real thing: card and Check (ACH) payments, your dual pricing, saved cards from your vault, and email receipts. Every charge settles to your own merchant account, same as always.
The software company (or your web developer) does the embedding with a small snippet; you stay in control because the whole thing runs on a key that YOU create, restrict, and can shut off at any moment.
The embed ships clean by default - just the terminal card with a small “Payments powered by Merchant360” mark under the payment button, so it sits naturally inside any product. If the host software wants your business name shown above the terminal, it can add &header=1 to the embed address.
Have Handpoint card readers? The embed offers a device mode automatically: your staff picks a reader (or stays locked to their assigned one) and the customer taps or dips on the physical terminal - the card never touches the host software at all.
Creating an embed key
Go to Billing Tools → Settings and open the Embedded terminal card. Create a key and give it the website addresses it's allowed to run on - for example yourpractice-software.com. The key is shown to you exactly once; copy it and hand it to the software vendor or developer doing the embedding.
- 1Billing Tools → Settings → Embedded terminal → Create key.
- 2Enter the domain(s) the terminal may appear on. A *.example.com entry covers every subdomain.
- 3Copy the key now - for security we only ever show it this one time.
- 4Give the key and the embed address to your software vendor or developer.
Create a separate key per product or vendor. If a relationship ends, you revoke that one key and nothing else is touched.
Test keys
Create a test key (it starts with vtk_test_) and the vendor can build and demo the whole integration without a single real charge. When everything looks right, swap in a live key - nothing else changes.
Where the payments show up
Charges taken through the embedded terminal are your normal payments: they appear in Transactions, settle in your batches, and follow your dual pricing and fraud rules like any other virtual-terminal charge. Receipts send from your business the same way too.
See your transactionsFor the software vendor: pulling payments back
The host software usually wants the payments back for its own reporting. Two ways, both under Developers in Merchant360:
- 1Webhooks - register a webhook and Merchant360 pushes payment events (charge succeeded, refunded, and more) to the software the moment they happen, signed so the software can verify they're real.
- 2Reporting API - the software can also pull transactions on its own schedule with a Merchant360 API key: list payments, look one up, filter by date - everything needed to display and reconcile activity inside their product.