Skip to main content
DatecsPay is a card payment provider you can use instead of Stripe or myPOS, built on BORICA’s hosted checkout. When a customer pays for a booking, class, membership, or outstanding balance, they are redirected to BORICA’s secure page to enter their card details (with EMV 3-D Secure), then return to 1Club once the payment completes. An owner or admin sets it up once with your gym’s own BORICA credentials.
If your organization trades through more than one company, each company connects its own BORICA terminal. Pick the company under Billing entity at the top of the DatecsPay page before you save or deactivate anything. The line under the picker reminds you that payments for that company’s gyms settle to the account you are setting up. The picker only appears when you have more than one billing entity. See Billing entities.

​
When to use it

DatecsPay suits a gym whose bank or acquirer has provisioned a BORICA terminal. Card data never touches 1Club servers, and every request is signed with your own RSA key. Payment status comes back on its own: through the cardholder’s browser on return, a signed BORICA notification, and a reconciliation sweep that catches anyone who closes the tab early. Unlike Stripe and myPOS, DatecsPay has no free shared sandbox. Both the Test and Live environments run against BORICA with your own credentials. Only the terminal and gateway differ between them. Typical uses:
  • A gym already banking with BORICA - take card payments online through the BORICA terminal your bank issued, with no Stripe or myPOS account.
  • Rehearsing checkout before going live - run the full checkout against BORICA’s test gateway with your test terminal, where no real money moves, then switch to Live.
  • A member who closes the tab mid-payment - the membership still settles, because the reconciliation job confirms the charge with BORICA within a few minutes, with no staff action.

​
Before you start

  • A paid plan. DatecsPay is a paid-plan integration. On the Free plan and during the free trial, Activate is greyed out until you upgrade.
  • BORICA credentials for the environment you want. Both Test and Live need a Terminal ID (TID), a Merchant ID (MID), your RSA private key, and BORICA’s public certificate. BORICA issues a separate set for each environment, so keep the two sets apart.
  • A free hosted-checkout slot. Each company can run only one hosted-checkout provider at a time. If myPOS hosted checkout is active for the company, deactivate myPOS first, or untick its Online capability if you only use it for terminals.
Configuring DatecsPay requires the settings.manage.organization permission. Viewing its settings requires settings.read.organization.

​
Where to get your DatecsPay credentials

DatecsPay credentials come from BORICA (through your bank or acquirer), not from 1Club. When your DatecsPay/BORICA terminal is provisioned you receive: Generate your key pair and register it with BORICA before you configure 1Club, and download the matching BORICA certificate for the environment you are setting up.

​
Activate DatecsPay

  1. Go to Settings > Integrations.
  2. Under Payments, click Activate next to DatecsPay. 1Club opens the DatecsPay page. Nothing is saved until you click Save.
  3. Choose an Environment:
    • Test - runs against BORICA’s test gateway.
    • Live - processes real payments against BORICA production.
    BORICA gives you different credentials for each environment, so enter the set that matches the one you choose.
  4. Enter your Terminal ID (TID) and Merchant ID (MID).
  5. Check the Merchant name and Merchant website. 1Club pre-fills these from your organization’s name and website, but you can edit them if BORICA registered a different name or URL.
  6. Paste your Merchant private key (PEM) and BORICA public certificate (PEM). If your key file is protected with a passphrase, enter it in Private key passphrase. 1Club uses it once to decrypt the key and never stores it.
  7. Click Save. The page shows Active and the environment, Test or Live, next to the title.
  8. Click Test configuration to check that the stored key and certificate are well-formed. The button is available once DatecsPay is saved.
The private key and certificate are stored encrypted and shown back to you as masked fields (•••••• (saved - leave blank to keep)). When you edit the configuration later, leave them blank to keep the existing values. Only paste a value if you are replacing it.
Your country and time-zone offset are not part of this form. 1Club derives them automatically from your organization settings and sends them to BORICA at checkout.

​
Configuration fields

Capabilities are limited to online hosted checkout, which is always on. There is no in-person terminal option.

​
Test vs. live environment

  • Test runs against BORICA’s test gateway with your test terminal. No real money moves, so you can rehearse the full checkout flow.
  • Live runs against BORICA production with your live terminal. Real payments are processed and settled to your account.
There is no credential-free sandbox. Both environments need a full credential set, and the TID, key, and certificate are different for each. DatecsPay keeps one credential set per company, for the environment you saved. When you switch Environment, the page clears the Terminal ID (TID), key, passphrase, and certificate fields. To save, enter the TID, private key, and BORICA certificate issued for the new environment. If you leave the key or certificate blank, the page asks for the one issued for that environment. Your saved set for the old environment is replaced, so keep a copy if you plan to switch back.

​
Test configuration

The Test configuration button checks that your saved credentials are complete and well-formed: that the private key and BORICA certificate are valid and the gateway for your environment resolves. It records the time of the last successful check. On success it shows “DatecsPay configuration looks valid”.
This check runs locally and does not contact BORICA or move any money. It catches a malformed key or a missing field, but it can’t confirm that BORICA recognizes your TID or merchant. The first real proof that credentials are correct is a successful test payment through hosted checkout.

​
What syncs

  • Payments created in 1Club open a BORICA hosted-checkout page that the customer is redirected to.
  • After payment, the status returns to 1Club through up to three paths, so a payment settles even if one path fails:
    1. Browser return - BORICA posts the signed result back through the cardholder’s browser when they return to 1Club, and 1Club verifies the signature and settles the payment.
    2. Signed notification - BORICA can also notify 1Club server to server. The notification’s signature is verified against your BORICA certificate before it is processed.
    3. Reconciliation - a background job runs every 5 minutes and confirms any payment still pending (for example because the customer closed the tab before returning) with a direct status check to BORICA.
  • The payment status and BORICA transaction references are recorded on the 1Club payment, and any linked charges and bookings are settled automatically.
  • Every path is matched to the same payment by a unique reference, so a redelivered notification or an overlapping reconciliation never double-charges or double-settles.
DatecsPay has no shareable payment link. The Send myPOS payment link action on a charge works with myPOS only, so on DatecsPay a member pays through the checkout in the portal, the app, or your website rather than from a link you send them. If sending a pay-by-link is central to how you collect, myPOS is the better fit.

​
Refunds

1Club does not push refunds to BORICA. Refund a DatecsPay payment from your BORICA/acquirer side, then reconcile the charge in 1Club.

​
Deactivate

  1. Pick the company under Billing entity, if you have more than one.
  2. Click Deactivate at the top of the DatecsPay page.
  3. Confirm in the Deactivate DatecsPay? dialog. It says DatecsPay stops working and its settings are deleted. With more than one billing entity, it also says the change applies to the selected company only.
You stay on the DatecsPay page afterwards, with the form reset. Your stored credentials for that company are cleared, so activating again means entering them again. If 1Club can’t deactivate DatecsPay, the reason shows in the dialog.

​
Troubleshooting

  • Activate is greyed out - your organization is on the Free plan or the free trial. Upgrade to a paid plan to activate payments.
  • Test configuration fails - confirm the Merchant private key (PEM) and BORICA public certificate (PEM) are valid PEM and that you pasted the certificate for the environment you selected (test and production certificates differ).
  • Save asks for the key and certificate again - you changed Environment. BORICA issues a separate set per environment, so paste the key and certificate for the environment you selected.
  • Customers see a signature error on the checkout page - the public key registered with BORICA doesn’t match the private key on file, or the TID belongs to a different environment. Re-check the key pair registered with BORICA and confirm the TID matches your selected environment.
  • Payment succeeded on BORICA but the charge stays unpaid in 1Club - this usually resolves on its own: the reconciliation job confirms pending checkouts within a few minutes. If it persists beyond that, re-check that your BORICA certificate is current.
  • Live payments fail but test works - confirm you are in the Live environment and entered live credentials (a production TID and the production BORICA certificate, not the test ones).
  • “myPOS is already enabled” - only one hosted-checkout provider can be active per company. Deactivate myPOS for that company, or untick its Online capability, then save DatecsPay again.

​
Worked examples

Bulgarian gym already banking with BORICA. A fitness gym whose bank issued it a BORICA e-commerce terminal generates an RSA key pair, registers the public key with BORICA, and downloads the production certificate. It activates DatecsPay, selects Live, enters its TID and MID, pastes the private key and certificate, saves, and runs Test configuration. One real court booking confirms hosted checkout settles the charge. A member who closes the tab mid-payment. A member pays for a membership on BORICA’s page but closes the browser before returning to 1Club, so the payment briefly shows as pending. Within a few minutes the reconciliation job checks the status with BORICA, confirms the charge, and settles the membership, with no staff action needed.

​
Tips & best practices

  • Keep your test and production credential sets clearly separated. The TID, key, and BORICA certificate differ per environment, and mixing them is the most common cause of signature errors.
  • Remember that Test configuration is a local check only. It can’t confirm BORICA recognizes your terminal, so always follow it with a real test payment.
  • Leave the masked private key and certificate fields blank when editing later. Only paste a value when you are deliberately replacing it.
  • Decide up front whether each company takes online card payments through DatecsPay or myPOS. Only one hosted-checkout provider can run per company.
  • Integrations - the full integration catalog and how activation works.
  • Billing entities - the companies you trade through, each with its own payment accounts.
  • myPOS - the other hosted-checkout provider (myPOS Online can’t run alongside DatecsPay for the same company).
  • Stripe - card and wallet payments with test and live modes.
  • Charges - where payable charges live.
  • Payments - the payment records DatecsPay settles.