SafeCharge (deprecated)
API Version
Minimum required API version: 1.2.0
Payment Methods
The following table lists all supported payment methods. Contact your SafeCharge account representative if you require additional payment methods.
| Payment Method | Payment Method Type |
|---|---|
| MASTERCARD | Cards |
| VISA | Cards |
Currencies
AED, ARS, AUD, AZN, BGN, BHD, BND, BRL, BYN, BYR, CAD, CHF, CLP, CNH, CNY, COP, CRC, CZK, DKK, DZD, EEK, EGP, EUR, GBP, GEL, HKD, HRK, HUF, IDR, INR, IQD, ISK, JOD, KGS, KRW, KWD, KZT, LBP, LTL, LVL, MAD, MDL, MXN, MYR, NIS, NOK, NZD, OMR, PEN, PHP, PKR, PLN, QAR, RON, RSD, RUB, SAR, SEK, SGD, SKK, THB, TND, TRY, TWD, UAH, USD, UYU, VEF, VND, YEN, YER, ZAR
Features
The following table provides an overview of all supported and non-supported features.
| Feature | Supported |
|---|---|
 3DS 1.0 External | No |
| 3DS 1.0 Internal | Yes |
| 3DS 2.0 External | No |
| 3DS 2.0 Internal | No |
| Installments | No |
| Level 2 and 3 Data | No |
| Retrieve Supported Payment Methods | No |
| Statement Soft Descriptor | Yes |
| Stored Credentials Flag | Yes |
| Transaction Processing without CVV | No |
Requests
The following table lists all supported requests for card-based transactions. Use the bodybuilder to create a sample request body for each request type.
| Request | Partial/Multiple | Mode |
|---|---|---|
| Authorize | Partial and multiple are not supported | Synchronous |
| Capture | Both partial and multiple are supported | Synchronous |
| Charge | Not Applicable | Synchronous |
| Credit | Partial and multiple are not supported | Synchronous |
| Refund | Both partial and multiple are supported | Synchronous |
| Void | Not Applicable | Synchronous |
Setup Procedures
A SafeCharge account can be configured to use either Charge or Authorize, but not both. Any request you create in PaymentsOS should therefore match the request type you chose to use in SafeCharge (do not create an Authorize request in PaymentsOS if you use Charge in SafeCharge and, vice versa, do not create a Charge request in PaymentsOS if you use Authorize in SafeCharge).
Note
Failing to configure a matching request type will cause unwanted behavior, such as an actual transfer of funds when issuing an Authorize request or a mismatch in request statuses between PaymentsOS and SafeCharge.The following table lists the setup procedures that are specific to this provider.
| Configuration | Required/Optional |
|---|---|
In the PaymentsOS Control Center, configure the following credentials:
| Required |
| In your SafeCharge account, make sure to set the HTTP method for IPN notifications to POST. | Required |
| In the PaymentsOS Control Center, register webhooks to be notified when a transaction changes its status. This is recommended if you enabled 3DS. | Optional |
| In your SafeCharge account, create separate merchant accounts if you want to use both Charge and Authorize requests. This requires that you create separate provider configurations in the PaymentsOS Control Center as well. Note: With SafeCharge you can use either Charge or Authorize, but not both. If you require both, create a separate merchant account for each request type. | Optional |
In your SafeCharge account, enable the transaction request types you would like to use:
| Optional |
In your SafeCharge account, you can configure your risk settings so that the following fields are optional:
| Optional |
| In your SafeCharge account, enable passing of a soft descriptor in your payment requests. Note: This is known as a Dynamic Descriptor in your SafeCharge account. | Optional |
Testing
Use the testing resources provided in the SafeCharge documentation.