A US private medical practice can have a cross-border card-payment workflow without operating an overseas location. Its payment processor may use infrastructure abroad, a payment platform may rely on foreign subcontractors, or a support team outside the United States may have remote access to payment systems.
The owner’s question is not simply, “Is this vendor PCI compliant?” It is: Where does card information go, who can access it, and what responsibilities remain with the practice?
PCI DSS—the Payment Card Industry Data Security Standard—concerns payment-card data security. It is not a general standard for every international bank transfer. Paying an overseas supplier by bank transfer raises different questions from accepting a patient’s card through a provider with overseas operations.
This guide focuses on the decision a staffed medical practice needs to make before approving or changing that arrangement. Use it to prepare a data-flow worksheet, request provider documentation, and obtain scope and validation guidance from your merchant acquirer and qualified PCI specialists. It is not a determination that a particular setup is compliant.
Identify what actually crosses the border
Start by separating the movement of money from the movement of card information. A deposit into a US practice bank account does not establish that every part of the payment workflow remains in the United States. Conversely, an international bank payment does not automatically create a PCI DSS issue.
| Practice situation | Question to investigate | Appropriate next step |
|---|---|---|
| A patient uses a card issued outside the United States | Does the existing acceptance process change, or is only the card issuer abroad? | Ask the acquirer whether the arrangement changes any acceptance or validation obligations. |
| A payment provider processes or stores information abroad | Which services, systems, and countries are involved? | Request a data-flow description and supporting PCI documentation. |
| Overseas support personnel access a payment application | What can they view, export, change, or control remotely? | Review access and responsibility boundaries with the provider and PCI specialist. |
| The practice pays an overseas vendor by bank transfer | Is any payment-card information involved? | Keep bank-transfer controls separate from the PCI DSS review. |
| An overseas administrative contractor helps collect patient balances | Does the contractor receive card details or access a system that can affect payment security? | Map the actual workflow before treating the contractor as outside the review. |
Do not use a vendor’s headquarters address as a substitute for this analysis. Ask about processing, storage, backups, remote support, and subcontractors separately.
Map card information from collection to reconciliation
Have the practice manager walk through each payment channel with the staff who actually use it. Include front-desk transactions, telephone payments, online payment links, stored payment methods, refunds, and disputed payments where applicable.
Document ordinary work and exceptions. A hosted payment page may keep card entry outside the practice’s systems, while an exception process brings card details into email, handwritten notes, or call recordings. Those workarounds matter.
Card-payment data-flow worksheet
The entries below are illustrative workflow prompts, not findings about any particular practice or vendor. Replace them with your actual systems, responsible parties, and confirmed locations. Do not enter real card numbers or security codes in the worksheet.
| Workflow stage | What to record | Cross-border question | Evidence or owner |
|---|---|---|---|
| Front-desk card acceptance | Device, application, location, and whether staff can see or enter card details | Can an overseas team remotely access the device or connected application? | Practice manager; device and provider documentation |
| Telephone payment | Who receives details, where they enter them, and whether calls or screens are recorded | Does a foreign contractor or support team hear, view, or retrieve the information? | Front-desk lead; call and screen-recording settings |
| Online payment | Where the patient enters details and which party operates that page | Where is the service operated, and which subcontractors support it? | Website administrator; payment-provider flow diagram |
| Stored payment method | Whether the practice sees a token, masked number, or accessible full card number | Who operates the storage service, and who can access the underlying information? | Provider documentation; PCI specialist review |
| Refunds and disputes | Portal permissions, attachments, exports, and supporting records | Can overseas personnel download records or change refund settings? | Finance lead; access list and dispute procedure |
| Settlement and bookkeeping | Reports used to match receipts, fees, refunds, and bank deposits | Do exported files contain unnecessary card information, and who receives them? | Bookkeeper; sample report with sensitive information removed |
For each row, add the practice’s legal entity, merchant account identifier, location, system owner, and unresolved questions. List countries for processing, storage, and remote access separately. If a location is unknown, record “not confirmed” rather than assuming it is domestic.
Include the systems around the payment
Ask a qualified specialist which connected systems can affect payment security. Do not limit the discussion to the card terminal itself.
Relevant questions may include:
- Can practice staff change the payment page or payment-link destination?
- Can a support user change account permissions or export transaction information?
- Do recordings, screenshots, support tickets, or browser tools capture card details?
- Are card details being copied into patient-account notes or spreadsheets?
- Does a shared administrative team access payment accounts for multiple practice entities?
Avoid drawing your own scope conclusion from labels such as “encrypted,” “tokenized,” or “cloud-based.” Ask what the feature does in the actual configuration and what evidence supports the claimed effect on scope.
Request a provider evidence package
A sales statement that a provider is “PCI compliant” is not enough to explain which services were assessed or what the practice must still do. Request documentation for the particular product, contracting entity, and service configuration you plan to use.
The PCI Security Standards Council provides PCI standards and supporting resources. Have the acquirer or a qualified PCI specialist interpret the documentation against your actual workflow rather than relying on a badge or general marketing page.
| Document or explanation to request | What the practice should check |
|---|---|
| Applicable Attestation of Compliance and service description | Does the assessed entity and service match the provider and product in your contract? What assessment period and scope are stated? |
| Written responsibility matrix | Which controls belong to the provider, which remain with the practice, and which depend on both parties? |
| Data-flow and service-boundary description | Where does card information enter, move, and reside? Which systems and parties are included? |
| Subcontractor and remote-support information | Which other parties participate, from which countries, and with what access? |
| Configuration and implementation instructions | Which settings or operating procedures must the practice maintain for the proposed arrangement? |
| Incident escalation and change-notification procedures | Who is reachable outside US business hours, and how will relevant service changes be communicated? |
| Exit and data-handling terms | What happens to access, stored information, and reporting when the practice changes providers? |
A provider may offer a controlled review process rather than freely distributing detailed security documents. Ask how your acquirer or specialist can review the necessary evidence. If a material question remains unanswered, keep it open in the approval record.
sbb-itb-17e8ec9
Take an acquirer-question checklist to the review
Your merchant acquirer—the institution supporting your merchant acceptance arrangement—is a key contact for validation expectations. If your day-to-day contact is a processor or reseller, ask who can provide an authoritative response for the merchant account.
Send the worksheet and provider evidence before the discussion. Request written answers to these questions:
- Which merchant accounts and entities are covered? Identify every practice entity and location using the proposed service.
- What is the practice’s validation route? Ask which assessment or reporting method applies to this specific setup, including the applicable Self-Assessment Questionnaire if appropriate.
- Which assumptions support that route? Confirm payment channels, system connections, provider services, and staff activities that the answer depends on.
- How does overseas access affect the review? Describe remote support and subcontractor access, not just the provider’s office address.
- What provider evidence is acceptable? Ask whether the supplied documentation covers the service actually being used.
- What remains the practice’s responsibility? Request clarity on implementation, access management, staff procedures, testing, and submission requirements as applicable.
- Does the proposed design qualify for any claimed scope reduction? Have a specialist evaluate hosted pages, tokenization, or encryption claims rather than assuming they eliminate obligations.
- What changes require reassessment? Include new payment channels, recording tools, locations, contractors, and provider configurations.
- What should happen after a suspected incident? Confirm contacts, escalation instructions, and coordination with qualified responders.
Do not select a questionnaire based only on a vendor’s assurance that other medical practices use it. The relevant facts are your practice’s configuration and the validation expectations for its merchant arrangement.
Keep financial reporting useful without copying card details
The finance team needs to explain patient-payment receipts, processing fees, refunds, disputes, and settlement timing. That does not mean full card details belong in the bookkeeping file.
Use provider transaction references and appropriately limited reports to connect payment activity to bank deposits. Review sample exports before distributing them to bookkeepers, location managers, or outside advisers. If a report contains unnecessary sensitive information, ask whether a more limited version is available.
For a multi-location or multi-entity practice, maintain a clear mapping between:
- The merchant account and responsible legal entity.
- The location or department receiving credit for the receipt.
- The bank account receiving settlement.
- Fees, refunds, and dispute adjustments associated with that activity.
This mapping supports reconciliation and location-level financial reporting; it does not establish PCI scope. Shared access across entities still needs its own security review.
Keep card-security questions separate from patient-privacy questions as well. Where financial work involves patient information, assess the appropriate privacy safeguards and service relationships. HHS guidance on covered entities and business associates addresses that separate framework. PCI documentation does not resolve HIPAA responsibilities, and HIPAA arrangements do not resolve PCI responsibilities.
Do not send patient-identifiable information or card details through ordinary Slack messages or general-purpose AI tools to resolve a payment question.
Turn the review into an approval decision
Maintain a short decision record with an accountable owner, supporting evidence, open issues, and follow-up actions.
| Finding | Practical decision |
|---|---|
| Workflow and responsibilities are documented, with acquirer guidance obtained | Proceed subject to completing the identified implementation and validation work. |
| Provider evidence does not clearly cover the proposed service | Request clarification before relying on the provider’s PCI claim. |
| Overseas support access is unclear | Obtain the access description and specialist review before expanding that access. |
| Staff use an undocumented workaround to collect card information | Escalate it for prompt review and establish an approved collection process. |
| A new location or payment channel is added | Revisit the worksheet and ask whether scope or validation expectations change. |
Keep compliance approval separate from the commercial comparison. Processing costs, settlement timing, refund handling, and reporting quality matter to practice finances, but favorable terms do not answer unresolved card-security questions.
Before go-live, confirm that staff know the approved payment process, who owns provider access, and how to escalate unexpected card information or suspected exposure. Arrange follow-up reviews based on acquirer guidance, specialist advice, contractual requirements, and material workflow changes rather than inventing a universal audit schedule.
The owner’s takeaway
Cross-border card-payment review is a responsibility-mapping exercise, not a country blacklist or a vendor-badge check. Identify where card information enters the practice workflow, who can handle it, and which evidence supports the proposed arrangement.
Outsourcing payment processing does not by itself settle the practice’s responsibilities. The strongest approval record connects the actual data flow, the provider’s documented role, and the acquirer’s validation expectations—with unresolved technical questions referred to qualified PCI specialists.