Overview
EBizCharge is a fully integrated payment processing solution within 1place that allows businesses to securely accept, manage, and track credit card payments throughout the sales process.
Once the EBizCharge integration is set up, payment-related activities can be managed directly within 1place, helping keep customer payment information and transaction activity connected to the corresponding customer and sales records.
With EBizCharge, users can:
- Manage Customer Payment Methods - Add and manage customer payment methods within 1place.
- Process Credit Card Payments - Accept credit card payments directly from Sales Orders and Invoices.
- Generate Payment Links - Create Email Pay / Payment Links that can be sent to customers so they can make a payment online.
- Track Transactions - View credit card transaction history and payment activity within 1place.
- Accept Customer Portal Payments - Allow customers to securely make credit card payments through the Customer Portal.
- Request Payment Methods - Send requests to customers to provide or save a payment method.
- Process Refunds - Process refunds for applicable credit card transactions.
The EBizCharge integration connects these payment activities with the customer's records and sales transactions in 1place, providing a centralized way to manage credit card payments without requiring users to leave the system for everyday payment tasks.
This article covers the complete EBizCharge workflow in 1place, including:
- Setting up an EBizCharge account.
- Connecting the EBizCharge account to 1place.
- Managing customer payment methods.
- Processing credit card payments.
- Sending payment links and accepting Customer Portal payments.
- Viewing transaction history.
- Requesting payment methods.
- Processing refunds.
- When creating or updating a user, review the applicable security settings to make sure the user's access matches their responsibilities.
Getting Started
How to Sign Up for an EBizCharge Account
Before using EBizCharge to process credit card payments through 1place, your business must first establish an EBizCharge account.
If you are interested in using EBizCharge with 1place, you can sign up with assistance from your dedicated 1place Customer Support team.
To get started:
- Create a support ticket by sending an email to support@onesourcesoftware.com to let your dedicated customer support team know that you would like to sign up for an EBizCharge account.
- 1place will introduce you to EBizCharge and initiate the referral process.
- Wait for EBizCharge to contact you. An EBizCharge Sales Representative will reach out to you to discuss the account setup and offer an EBizCharge demo.
- Prepare your credit card processing statements. EBizCharge may request your most recent three months of credit card statements as part of the account setup process. Have these statements available when requested.
- Complete the EBizCharge signup and onboarding process with the EBizCharge team.
- Once your EBizCharge account is established, obtain the following credentials from EBizCharge:
- API User ID
- Security ID
- Password
- Once you have these credentials, you can proceed with setting up the EBizCharge integration in 1place.
Note: EBizCharge handles the payment-processing account setup and approval. The specific information or documentation required during the signup process may vary.
Need help getting started? Create a support ticket by sending an email to support@onesourcesoftware.com to request assistance with signing up for EBizCharge.
How to Set Up the EBizCharge Integration in 1place
How to Set Up EBizCharge Integration in 1place
After your EBizCharge account has been established and you have received the required credentials, enter them in the EBizCharge integration settings in 1place.
- In 1place, go to Sales > Integrations > EBizCharge (Credit Card).
- Select General Settings.

- Enter the following EBizCharge credentials:
- API User ID
- Security ID
- Password
- Review the information entered to make sure the credentials are correct.
- Click Save.
- Start testing the integration using the Test Cards from EBizCharge. Follow the articles below to start testing adding a payment method and processing credit card payments. If you need further assistance, contact your dedicated 1place Customer Support.
To process a payment using a card already saved for the customer:
- On the Invoice screen, click Payment Info.
- Click Receive/Edit Payments. The Payments window will appear.
- Under Payment Method, select Credit Card.
- Select a card from the Cards on File dropdown. The dropdown displays all saved cards available for the customer.

- Review the card information and make sure all details are accurate. The CVV/Security Code must be entered when processing the payment. This information should be obtained from the customer.
- Review the Amount Tendered and make sure the payment amount is correct.
- Click Authorized Card and Apply Payment to authorize the card and apply the payment to the invoice.
How to Use a New Card for Payment
A new card can be used to process a credit card payment by selecting Add New Card during the payment process.
- On the Invoice screen, click Payment Info.
- Click Receive/Edit Payments. The Payments window will appear.
- Under Payment Method, select Credit Card.
- Click Add New Card. The Add New Card EBizCharge form will appear.

- Enter the required card information and make sure all details are accurate. The CVV/Security Code must be entered when processing the payment. This information should be obtained from the customer.

- Review the Amount Tendered and make sure the payment amount is correct.
- Click Authorized Card and Apply Payment to authorize the card and apply the payment to the invoice.
Understanding Payment Results
After Authorized Card and Apply Payment is selected, the system will process the credit card transaction and display the payment result. Review the result to confirm whether the payment was successfully authorized and applied to the invoice.
Customer Payment Experience
How to Generate an Email Pay / Payment Link
The Email Pay option allows you to send the customer a secure payment link where they can complete the invoice payment using a saved card or a new card.
- On the Invoice screen, click Payment Info.
- Click Receive/Edit Payments. The Payments window will appear.
- Under Payment Method, select Email Pay.

- Verify the customer's email address. The system will usually populate the customer's primary email address saved on file. Update the email address if the customer provides a different one.
- Click Pay via Email. A confirmation message will appear indicating that the payment link has been sent.
- Have the customer check their email for the payment link.

- In the email, the customer should click the Click to Pay button.

- A secure payment form will open in a new tab. The customer can select a saved card or enter a new card. The CVV/Security Code is required.

- Once the card is selected or entered, the customer clicks Pay Now to complete the invoice payment.
How to Sync Email Pay Payments with 1place
Payments completed through Email Pay are not automatically synchronized with the invoice in 1place. The e-payment must be fetched from EBizCharge before it is reflected in 1place.
There are two ways to fetch e-payments:
Fetch E-Payments When Opening an Invoice
When an Invoice is opened, 1place automatically fetches available e-payments from EBizCharge.
Manually Fetch E-Payments
- Go to Sales > Integrations > EBizCharge (Credit Card).
- Select General Settings.
- Locate the Fetch E-Payments button below the Password field.
- Click Fetch E-Payments to retrieve available e-payments.
How to Automatically Fetch E-Payments
An Automated Job can be configured in 1place to automatically fetch e-payments at a set interval. This eliminates the need to manually fetch e-payments.
For example, an Automated Job can be configured to Fetch E-Payments every 30 minutes.
This allows Email Pay transactions to be regularly retrieved from EBizCharge and synchronized with 1place.
How Customers Pay Through the Customer Portal
Customers can also pay for their orders using a credit card through the Customer Portal.
- After adding items to the cart, click Proceed to Checkout.
- On the Secure Checkout screen, under Paying With, select Pay with Credit Card.

- Select a card from the Cards on File dropdown, or click Add New Card to enter a new card.
- Review the card information and make sure all details are accurate. The CVV/Security Code must be entered when processing the payment.
- Click Submit Order & Pay to complete the order and payment.
Summary of the Customer's Payment Experience
Customers can complete credit card payments through either an Email Pay payment link or the Customer Portal. In both methods, customers can use a saved card or enter a new card, with the CVV/Security Code required to complete the payment.
Managing Transactions
How to View Credit Card Transaction History
To view the history of credit card transactions:
- Go to Sales > Integrations > EBizCharge (Credit Card) > All Transaction History.
- Select the From and To dates to specify the transaction date range.
- Click Get Transaction to display the transactions within the selected date range.

The transaction history displays the following information:
- Invoice # - The invoice associated with the transaction.
- Transaction Date - The date and time the transaction was processed.
- Customer # - The customer associated with the transaction.
- Result - The result of the transaction, such as Approved.
- Auth Amount - The amount authorized for the transaction.
- Remaining Balance - The remaining balance associated with the transaction.
- Reference # - The reference number assigned to the transaction.
- Card Code Result - The result of the card security code verification.
- Batch Reference - The batch reference associated with the transaction.
- Batch # - The batch number associated with the transaction.
- AVS Result - The result of the Address Verification System (AVS) check.
- Status - The current status of the transaction.
How to Refund a Credit Card Payment
Credit card payments can be refunded directly from the invoice where the payment was applied.
- Open the Invoice.
- Click Receive/Edit Payments.
- At the bottom of the Payments window, locate the list of payments made on the invoice.
- Under Action, click the Refund button (reverse icon) for the payment you want to refund.
- Complete the payment details:
- Select the Payment Method to be used for the refund from the dropdown.
- Confirm the Payment Date.
- Click Apply Payment.
Understanding Credit Card Transaction Statuses
The Status column in All Transaction History shows the current processing status of each credit card transaction. Understanding these statuses helps you determine whether a payment is still being processed, has been completed, or has been returned.
Approved
Approved indicates that the credit card transaction was authorized by the card issuer. The authorization confirms that the transaction was accepted for processing. An approved transaction may still go through additional processing before it is fully settled.
Pending
Pending indicates that the transaction has been authorized but has not yet been fully processed or finalized. Pending transactions are awaiting final processing and may remain in this status temporarily.
For example, All Transaction History may show:
- Result: Approved
- Status: Pending
This means the transaction was successfully authorized, but its processing has not yet been finalized.
Declined
Declined indicates that the card issuer did not approve the transaction. A transaction may be declined for reasons such as insufficient available funds, an exceeded credit limit, an expired card, or other restrictions on the card or transaction.
Settled
Settled indicates that the transaction has completed processing and has been settled.
Returned
Returned indicates that the transaction has been returned.
Refunded
Refunded indicates that a previously processed credit card payment has been returned to the customer's card.
Understanding Result vs. Status
The Result and Status columns provide different information:
- Result - Shows the response received when the credit card transaction was processed, such as Approved or Error.
- Status - Shows the transaction's current processing state, such as Pending, Settled, or Returned.
For example, a transaction may have a Result of Approved while its Status is Pending. This means the transaction was approved but is still completing its processing cycle. EBizCharge's documentation confirms that Result and Status are separate transaction properties, with Status values of Settled, Pending, and Returned.
Credit Card Information Handling and Security Guidelines
Purpose
This article provides guidelines for handling sensitive customer information, particularly credit card information, when communicating with customers, processing payments, or performing other business activities.
Anyone who handles customer payment information is responsible for protecting it from unauthorized access, disclosure, or misuse.
These guidelines support secure business practices and help reduce the risk of fraud, data exposure, and unauthorized transactions.
1. General Guidelines for Handling Credit Card Information
Protect Sensitive Information
Treat all customer payment information as confidential.
Access credit card information only when necessary for an authorized business purpose.
Never share credit card information with unauthorized individuals.
Never include full credit card numbers or card security codes (CVV/CVC) in ordinary emails, chat messages, support tickets, worklogs, or internal notes.
Never record credit card information in spreadsheets, documents, customer notes, or other unapproved storage locations.
Do not take screenshots, photographs, or screen recordings that expose sensitive payment information.
Never share account passwords, PINs, or authentication codes with other individuals.
Use Approved Methods for Collecting Payment Information
Collect and process credit card information only through approved payment systems or secure payment collection methods.
Do not ask customers to send credit card details through ordinary email, text messages, chat, or other unapproved communication channels.
If a customer needs to provide payment information, direct them to the organization's approved payment process.
Do not create alternative methods for collecting, transmitting, or storing payment information without authorization.
Never Retain Card Security Codes
The card security code, commonly called CVV or CVC, is the three- or four-digit code printed on a payment card.
Never store the CVV/CVC after a transaction has been authorized.
Do not record it in notes, documents, spreadsheets, email, or call recordings.
Customer permission does not make retaining the security code acceptable.
If a payment needs to be processed again, use the approved payment procedure rather than retrieving a previously recorded security code.
2. Handling Customer Payments
When accepting a credit card payment, follow the organization's approved payment procedures.
Before Processing a Payment
Verify the customer and the transaction being paid.
Confirm the amount to be charged and obtain the required customer authorization.
Ensure the payment is being processed through an approved system.
Use your own authorized account and never share login credentials.
If the customer wants their card saved for future payments, follow the approved card-on-file process and applicable authorization requirements.
When Taking Payments Over the Phone
Enter the customer's payment information directly into the approved payment interface or secure collection mechanism.
Do not write down card details for later entry.
Never ask the customer to send their card details through email or text as an alternative.
If calls are recorded, ensure the approved process prevents sensitive authentication data from being retained in the recording.
If payment information cannot be collected securely, stop and arrange an approved alternative.
When Accepting Payments in Person
Use the approved payment terminal or payment entry process.
Whenever available, allow the customer to enter their card information directly into the payment device.
Never photograph, copy, or retain the customer's card details.
Do not write down the card security code.
Confirm the transaction result and return the card to the customer promptly.
Saving Credit Cards for Future Use
When a customer requests that their card be saved for future transactions:
Use only the organization's approved card-on-file functionality.
Follow applicable customer consent and authorization requirements.
Do not store card information manually in customer notes, spreadsheets, documents, or other unapproved locations.
Never retain the CVV/CVC for future payments.
Limit access to saved payment methods to authorized personnel.
After Processing a Payment
Confirm the payment result through the approved payment system.
Verify that the payment is associated with the correct customer and transaction.
Provide an approved receipt or payment confirmation when appropriate.
Record the transaction reference and necessary business details rather than the full card number.
If the payment status is unclear, verify the original transaction before attempting another charge to avoid duplicate payments.
3. Handling Credit Card Information in Communications and Documents
Customer information may be shared or discussed during routine business communications. Care must be taken to ensure sensitive payment information is not inadvertently exposed.
Before sending an email, screenshot, document, or other attachment, verify that it does not contain exposed credit card information.
If a screenshot is needed for documentation, redact sensitive information before sharing it.
Do not copy credit card details into another system or document for convenience.
Do not forward messages containing sensitive payment information to other employees unless an approved procedure specifically requires it.
When discussing a payment, use the invoice number, transaction reference, payment status, or masked card number where appropriate.
Share customer information only with individuals who are authorized to receive it and have a legitimate business need.
4. Handling Refunds and Payment Disputes
Refunds, voids, and payment disputes must be handled through approved business procedures.
Verify the original transaction and the amount involved.
Confirm that you are authorized to perform the requested action.
Record the necessary transaction reference, status, and business details.
Never request a customer's CVV/CVC to issue a refund.
If a transaction appears unauthorized or suspicious, report it through the established internal process.
Do not process a second charge or refund until the status of the original transaction has been verified.
5. What to Do if Credit Card Information Is Exposed
If credit card information is accidentally shared, stored, or disclosed through an unapproved channel, take the following actions:
Stop further disclosure. Do not copy, forward, quote, or repeat the exposed information.
Report the incident promptly. Notify the appropriate supervisor or designated security contact and follow the organization's incident response procedure.
Secure the information. Follow the approved process for restricting access to or removing the exposed information, including applicable attachments and retained copies.
Do not use the exposed details. Never use the information to process a payment or conduct an unauthorized transaction.
Follow further instructions. Allow the designated personnel to assess the incident and determine the appropriate next steps.
Do not assume that deleting a visible message removes every copy of the information. Follow the approved procedure for the system where the information was exposed.
6. Quick Reference: Do and Don't
Do:
Protect customer payment information as confidential.
Use approved payment collection and processing methods.
Verify the customer, transaction, and payment amount before charging a card.
Use masked card numbers and transaction references when discussing payments.
Limit access to authorized personnel with a legitimate business need.
Report suspected exposure or unauthorized use promptly.
Don't:
Request full card details through ordinary email, chat, or support tickets.
Store CVV/CVC information after transaction authorization.
Keep credit card details in spreadsheets, documents, customer notes, or other unapproved locations.
Share payment information with unauthorized individuals.
Take or share screenshots containing exposed card details.
Process payments using information obtained through an unapproved channel.
7. Important Reminder
Protecting customer payment information is everyone's responsibility. Always use approved payment systems, follow established security procedures, and report potential data exposure promptly.
These guidelines support secure handling of customer information and do not replace applicable PCI DSS requirements, payment processor rules, organizational security policies, or legal obligations.
For additional information, refer to the PCI Security Standards Council.
The following list of test credit card numbers maybe used either on the Test Account or in Test Mode. The use of live credit card information in a test environment is strongly discourage. It is recommended that the card numbers on this page be used instead.
For more information on the response codes and their meanings see:
AVS Response Codes
CVV2 Response Codes
CAVV Response Codes
Card Level Codes
Please note that while the sandbox test platform does its best to simulate what you will see in production, there may be subtle differences depending on the platform being used. At this time we are only simulating the FDMS Nashville responses on the sandbox server.
AVS Responses
| Card Number | Expiration | CCV2 Code | AVS Response | CVV2 Response | CAVV Response | Card Level |
|---|---|---|---|---|---|---|
| 4000100011112224 | 0930 | 123 | YYY | M | A | |
| 4000100111112223 | 0930 | 321 | YYX | M | A | |
| 4000100211112222 | 0930 | 999 | NYZ | M | A | |
| 4000100311112221 | 0930 | 999 | NYW | M | A | |
| 4000100411112220 | 0930 | 999 | YNA | M | A | |
| 4000100511112229 | 0930 | 999 | NNN | M | A | |
| 4000100611112228 | 0930 | 999 | XXW | M | A | |
| 4000100711112227 | 0930 | 999 | XXU | M | A | |
| 4000100811112226 | 0930 | 999 | XXR | M | A | |
| 4000100911112225 | 0930 | 999 | XXS | M | A | |
| 4000101011112222 | 0930 | 999 | XXE | M | A | |
| 4000101111112221 | 0930 | 999 | XXG | M | A | |
| 4000101211112220 | 0930 | 999 | YYG | M | A | |
| 4000101311112229 | 0930 | 999 | GGG | M | A | |
| 4000101411112228 | 0930 | 999 | YGG | M | A | |
| 4000101511112227 | 0930 | 999 | NN | M | A | |
| 4000101611112226 | 0930 | 999 | N/A | M | A |
CVV2 Responses
| Card Number | Expiration | CVV2 Code | AVS Response | CVV2 Response | CAVV Response | Card Level |
|---|---|---|---|---|---|---|
| 4000200011112222 | 0930 | any | YYY | M | A | |
| 4000200111112221 | 0930 | any | YYY | N | A | |
| 4000200211112220 | 0930 | any | YYY | P | A | |
| 4000200311112229 | 0930 | any | YYY | S | A | |
| 4000200411112228 | 0930 | any | YYY | U | A | |
| 4000200511112227 | 0930 | any | YYY | X | A | |
| 5555444433332226 | 0930 | any | YYY | M | ||
| 5555444433332234 | 0930 | any | YYY | N | ||
| 5555444433332242 | 0930 | any | YYY | P | ||
| 5555444433332259 | 0930 | any | YYY | S | ||
| 5555444433332267 | 0930 | any | YYY | U | ||
| 5555444433332275 | 0930 | any | YYY | X | ||
| 371122223332225 | 0930 | any | YYY | M | ||
| 371122223332233 | 0930 | any | YYY | n/a | ||
| 371122223332241 | 0930 | any | CVV2 No Match (Decline) | |||
| 6011222233332224 | 0930 | any | YYY | M | ||
| 6011222233332232 | 0930 | any | YYY | N | ||
| 6011222233332240 | 0930 | any | YYY | P | ||
| 6011222233332257 | 0930 | any | YYY | S | ||
| 6011222233332265 | 0930 | any | YYY | U | ||
| 6011222233332273 | 0930 | any | YYY | X |
CAVV Responses
| Card Number | Expiration | CVV2 Code | AVS Response | CVV2 Response | CAVV Response | Card Level |
|---|---|---|---|---|---|---|
| 4000600011112223 | 0930 | 999 | YYY | M | 1 | A |
| 4000600111112222 | 0930 | 999 | YYY | M | 2 | A |
| 4000600211112221 | 0930 | 999 | YYY | M | 3 | A |
| 4000600311112220 | 0930 | 999 | YYY | M | 4 | A |
| 4000600411112229 | 0930 | 999 | YYY | M | 6 | A |
| 4000600511112228 | 0930 | 999 | YYY | M | 7 | A |
| 4000600611112227 | 0930 | 999 | YYY | M | 8 | A |
| 4000600711112226 | 0930 | 999 | YYY | M | 9 | A |
| 4000600811112225 | 0930 | 999 | YYY | M | A | A |
| 4000600911112224 | 0930 | 999 | YYY | M | B | A |
| 4000601011112221 | 0930 | 999 | YYY | M | C | A |
| 4000601111112220 | 0930 | 999 | YYY | M | D | A |
Card Level Responses
| Card Number | Expiration | CVV2 Code | AVS Response | CVV2 Response | CAVV Response | Card Level |
|---|---|---|---|---|---|---|
| 4000700011112221 | 0930 | 999 | YYY | M | A | |
| 4000700111112220 | 0930 | 999 | YYY | M | B | |
| 4000700211112229 | 0930 | 999 | YYY | M | C | |
| 4000700311112228 | 0930 | 999 | YYY | M | D | |
| 4000700411112227 | 0930 | 999 | YYY | M | G | |
| 4000700511112226 | 0930 | 999 | YYY | M | H | |
| 4000700611112225 | 0930 | 999 | YYY | M | I | |
| 4000700711112224 | 0930 | 999 | YYY | M | K | |
| 4000700811112223 | 0930 | 999 | YYY | M | S | |
| 4000700911112222 | 0930 | 999 | YYY | M | U | |
| 4000701011112229 | 0930 | 999 | YYY | M | G1 | |
| 4000701111112228 | 0930 | 999 | YYY | M | G2 | |
| 4000701211112227 | 0930 | 999 | YYY | M | J1 | |
| 4000701311112226 | 0930 | 999 | YYY | M | J2 | |
| 4000701411112225 | 0930 | 999 | YYY | M | J3 | |
| 4000701511112224 | 0930 | 999 | YYY | M | J4 | |
| 4000701611112223 | 0930 | 999 | YYY | M | K1 | |
| 4000701711112222 | 0930 | 999 | YYY | M | S1 | |
| 4000701811112221 | 0930 | 999 | YYY | M | S2 | |
| 4000701911112220 | 0930 | 999 | YYY | M | S3 |
Decline Responses
| Card Number | Expiration | CVV2 Code | Decline Code | Message |
|---|---|---|---|---|
| 4000300011112220 | 0930 | 999 | Declined | |
| 4000300001112222 | 0930 | 999 | 04 | Pickup Card |
| 4000300211112228 | 0930 | 999 | 05 | Do not Honor |
| 4000300311112227 | 0930 | 999 | 12 | Invalid Transaction |
| 4000300411112226 | 0922 | 999 | 15 | Invalid Issuer |
| 4000300511112225 | 0930 | 999 | 25 | Unable to locate Record |
| 4000300611112224 | 0930 | 999 | 51 | Insufficient funds |
| 4000300711112223 | 0930 | 999 | 55 | Invalid Pin |
| 4000300811112222 | 0930 | 999 | 57 | Transaction Not Permitted |
| 4000300911112221 | 0930 | 999 | 62 | Restricted Card |
| 4000301011112228 | 0930 | 999 | 65 | Excess withdrawal count |
| 4000301111112227 | 0930 | 999 | 75 | Allowable number of pin tries exceeded |
| 4000301211112226 | 0930 | 999 | 78 | No checking account |
| 4000301311112225 | 0930 | 999 | 97 | Declined for CVV failure |
Fraud Profiler Response
| Card Number | Expiration | Profiler Response |
|---|---|---|
| 4000301411112224 | 0930 | review |
| 4000301511112223 | 0930 | reject |
Referral Response
| Card Number | Expiration | CVV2 Code | AVS Response | CVV2 Response | CAVV Response | Card Level |
|---|---|---|---|---|---|---|
| 4000300111112229 | 0930 | 999 |
Slow Processing Cards
| Card Number | Expiration | Processing Time |
|---|---|---|
| 4000000011112226 | 0930 | 5s |
| 4000000011112234 | 0930 | 15s |
| 4000000011112242 | 0930 | 30s |
| 4000000011112259 | 0930 | 45s |
| 4000000011112267 | 0930 | 60s |

















