UNPKG

@monei-js/node-sdk

Version:

Node.js SDK for MONEI Digital Payment Gateway

77 lines (76 loc) 4.13 kB
/** * MONEI API v1 * The MONEI API is organized around REST principles. Our API is designed to be intuitive and developer-friendly. ### Base URL All API requests should be made to: ``` https://api.monei.com/v1 ``` ### Environment MONEI provides two environments: - **Test Environment**: For development and testing without processing real payments - **Live Environment**: For processing real transactions in production ### Client Libraries We provide official SDKs to simplify integration: - [PHP SDK](https://github.com/MONEI/monei-php-sdk) - [Python SDK](https://github.com/MONEI/monei-python-sdk) - [Node.js SDK](https://github.com/MONEI/monei-node-sdk) - [Postman Collection](https://postman.monei.com/) Our SDKs handle authentication, error handling, and request formatting automatically. You can download the OpenAPI specification from the https://js.monei.com/api/v1/openapi.json and generate your own client library using the [OpenAPI Generator](https://openapi-generator.tech/). ### Important Requirements - All API requests must be made over HTTPS - If you are not using our official SDKs, you **must provide a valid `User-Agent` header** with each request - Requests without proper authentication will return a `401 Unauthorized` error ### Error Handling The API returns consistent error codes and messages to help you troubleshoot issues. Each response includes a `statusCode` attribute indicating the outcome of your request. ### Rate Limits The API implements rate limiting to ensure stability. If you exceed the limits, requests will return a `429 Too Many Requests` status code. * * The version of the OpenAPI document: 1.7.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). * https://openapi-generator.tech * Do not edit the class manually. */ import type { PaymentBillingDetails } from './payment-billing-details'; import type { PaymentCustomer } from './payment-customer'; import type { PaymentShippingDetails } from './payment-shipping-details'; import type { PaymentTransactionType } from './payment-transaction-type'; /** * * @export * @interface RecurringPaymentRequest */ export interface RecurringPaymentRequest { /** * An order ID from your system. A unique identifier that can be used to reconcile the payment with your internal system. * @type {string} * @memberof RecurringPaymentRequest */ orderId: string; /** * The amount to collected by this subsequent payment. A positive integer representing how much to charge in the smallest currency unit (e.g., 100 cents to charge 1.00 USD). * @type {number} * @memberof RecurringPaymentRequest */ amount?: number; /** * Same as the `transactionType` parameter from [create payment](https://docs.monei.com/apis/rest/payments-create/). If not sent, it will default in the same transaction type used in the initial payment. * @type {PaymentTransactionType} * @memberof RecurringPaymentRequest */ transactionType?: PaymentTransactionType; /** * An arbitrary string attached to the payment. Often useful for displaying to users. * @type {string} * @memberof RecurringPaymentRequest */ description?: string; /** * * @type {PaymentCustomer} * @memberof RecurringPaymentRequest */ customer?: PaymentCustomer; /** * * @type {PaymentBillingDetails} * @memberof RecurringPaymentRequest */ billingDetails?: PaymentBillingDetails; /** * * @type {PaymentShippingDetails} * @memberof RecurringPaymentRequest */ shippingDetails?: PaymentShippingDetails; /** * The URL to which a payment result should be sent asynchronously. * @type {string} * @memberof RecurringPaymentRequest */ callbackUrl?: string; /** * A set of key-value pairs that you can attach to a resource. This can be useful for storing additional information about the resource in a structured format. * @type {object} * @memberof RecurringPaymentRequest */ metadata?: object; }