# Going live (/docs/server-to-server/going-live)

Test and production share one base URL. The environment is selected by the
credentials and the Brand ID you send, not by the host you call, so going live
is a matter of configuration and approval rather than re-pointing your
integration.

## Credentials [#credentials]

Production credentials can be issued for controlled production testing before a
merchant is fully live. A merchant go-live additionally depends on completing
the applicable onboarding and KYC requirements.

The **bearer token** is self-service: generate it in the Developers section of
the dashboard. The **S2S token is not**. It is issued by Precium to qualifying
merchants only, because submitting clear PAN data puts the integration in PCI
DSS SAQ-D scope. Request it well before you need it, in both environments.

<Callout type="warning">
Production portal users must use **email addresses different from those on the
test account**. The same address cannot hold both.
</Callout>

## Low-value production testing MID [#low-value-production-testing-mid]

A low-value production testing MID is a production configuration used to
validate end-to-end behaviour against real money, including reconciliation and
settlement.

| | |
|---|---|
| What it is for | Proving the full path works in production, including recon and settlement |
| What it is not | The merchant's live MID. Do not use it for normal processing |
| Descriptor | Fixed, and cannot be changed. This is an acquirer compliance requirement |
| Amounts | Use at least ZAR 1.00. See [amount limits](/docs/server-to-server/integration-guide#amount-limits) |

## Throughput and IP allow-listing [#throughput-and-ip-allow-listing]

The default limit is **10 transactions per second, per IP address**.

Before launch, send Precium:

- the **production IP addresses** that will call the API,
- the **production IP addresses** that will receive webhooks,
- the **transactions per second** you need.

Those addresses are allow-listed and capacity is provisioned against the agreed
figure. Traffic from an address that has not been submitted, or above the agreed
rate, will be rate limited.

## Merchant onboarding inputs [#merchant-onboarding-inputs]

Onboarding requirements depend on the merchant and its risk profile. It starts
with company registration and ownership information, and additional KYC and
beneficial-owner information is required before cross-border settlement, with
enhanced due diligence for higher-risk merchants.

For the acquiring-bank MID application, Precium may also request operational and
risk information:

- average delivery time,
- historic chargeback ratio,
- historic refund ratio,
- forecast transaction volume.

## Pre-integration testing [#pre-integration-testing]

Precium can provide Postman recipes once the payment-feature checklist is
complete. Dashboard access and API credentials are issued when the environment
is provisioned.

## Checklist [#checklist]

- [ ] Use the **S2S token** only for requests carrying clear PAN data, and the **bearer token** for everything else.
- [ ] Store **Brand IDs per merchant processing configuration**, not one per partner. A merchant with two MCCs has two Brand IDs.
- [ ] Implement the **3DS hand-off exactly as returned**. The ACS value is not a plain redirect URL. See [Completing a 3D Secure authentication](/docs/server-to-server/integration-guide#completing-a-3d-secure-authentication).
- [ ] Send amounts **in cents**, and at least **ZAR 1.00** for anything that must settle.
- [ ] Send **real customer and cardholder data** wherever it is available.
- [ ] Verify webhook signatures against the **raw request body**.
- [ ] Treat **webhooks as the state-change mechanism** and `GET /purchases/{id}/` as a current-state lookup.
- [ ] Agree **TPS** and submit **production API and webhook IPs** for allow-listing.
- [ ] Reconcile on **`gateway_transaction_id`**, keeping RRN, authorisation code and amount as secondary data. See [Reconciliation files](/docs/reconciliation).
- [ ] **Release** authorisation holds you do not intend to capture.
- [ ] Confirm the merchant's **card schemes, international-card rules, descriptor and settlement schedule**.