- Overview
- Countries & currencies
- Integration
- Process flows
- Testing
- Additional information
- Consumer experience
- Reporting
Integration
Using MyCheckout hosted payment pages
MyCheckout hosted payment pages are the optimal solution if you're looking for the quickest way to accept payments and provide a hassle-free experience for your consumers.
Before you begin
- Make sure you are boarded with Patagonia 365
- Build your server integration
- Make POST /{merchantId}/payments API call, submitting the required properties
Below, you'll find an example API call with the essential data. To add more information with additional properties, please visit to our API Reference.
Additionally, you can add hostedCheckoutSpecificInput object, featuring the following strings:
- returnUrl - the URL that the consumer is redirected to after the payment flow has finished.
- variant - the created styling of the checkout page tailored to your consumer's preferences.
- locale - the language that will be used for your hosted checkout page.
| Property | Data type | Required |
|---|---|---|
| order | object | yes |
| amountOfMoney | object | yes |
| currencyCode | string | yes |
| amount | integer | yes |
| references | object | yes |
| merchantreference | string | yes |
| customer | object | yes |
| merchantCustomerId | string | yes |
| billdingAddress | object | yes |
| countryCode | string | yes |
| cardPaymentMethodSpecificInput | object | yes |
| paymentProductId | integer | no |
| Card | object | yes |
| cardNumber | string | yes |
| expiryDate | string | yes |
| cardholderName | string | no |
| cvv | string | yes |
| hostedCheckoutSpecificInput | object | yes |
| returnUrl | string | no |
| locale | string | no |
| variant | string | no |