Monei 2.3.1__tar.gz → 2.3.2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (281) hide show
  1. {monei-2.3.1 → monei-2.3.2}/CHANGELOG.md +4 -0
  2. monei-2.3.2/Monei/__init__.py +33 -0
  3. {monei-2.3.1 → monei-2.3.2}/Monei/api/apple_pay_domain_api.py +2 -2
  4. {monei-2.3.1 → monei-2.3.2}/Monei/api/bizum_api.py +2 -2
  5. {monei-2.3.1 → monei-2.3.2}/Monei/api/payment_methods_api.py +2 -2
  6. {monei-2.3.1 → monei-2.3.2}/Monei/api/payments_api.py +5 -5
  7. {monei-2.3.1 → monei-2.3.2}/Monei/api/subscriptions_api.py +2 -2
  8. {monei-2.3.1 → monei-2.3.2}/Monei/api_client.py +2 -2
  9. {monei-2.3.1 → monei-2.3.2}/Monei/configuration.py +3 -3
  10. {monei-2.3.1 → monei-2.3.2}/Monei/exceptions.py +2 -2
  11. {monei-2.3.1 → monei-2.3.2}/Monei/model/activate_subscription_request.py +4 -4
  12. {monei-2.3.1 → monei-2.3.2}/Monei/model/address.py +2 -2
  13. {monei-2.3.1 → monei-2.3.2}/Monei/model/api_exception.py +2 -2
  14. {monei-2.3.1 → monei-2.3.2}/Monei/model/apple_pay_domain_register200_response.py +2 -2
  15. {monei-2.3.1 → monei-2.3.2}/Monei/model/bad_request_error.py +2 -2
  16. {monei-2.3.1 → monei-2.3.2}/Monei/model/bad_request_error_all_of.py +2 -2
  17. {monei-2.3.1 → monei-2.3.2}/Monei/model/bizum_validate_phone200_response.py +2 -2
  18. {monei-2.3.1 → monei-2.3.2}/Monei/model/cancel_payment_request.py +2 -2
  19. {monei-2.3.1 → monei-2.3.2}/Monei/model/cancel_subscription_request.py +2 -2
  20. {monei-2.3.1 → monei-2.3.2}/Monei/model/capture_payment_request.py +2 -2
  21. {monei-2.3.1 → monei-2.3.2}/Monei/model/confirm_payment_request.py +4 -4
  22. {monei-2.3.1 → monei-2.3.2}/Monei/model/confirm_payment_request_payment_method.py +2 -2
  23. {monei-2.3.1 → monei-2.3.2}/Monei/model/confirm_payment_request_payment_method_card.py +2 -2
  24. {monei-2.3.1 → monei-2.3.2}/Monei/model/create_payment_request.py +4 -4
  25. {monei-2.3.1 → monei-2.3.2}/Monei/model/create_subscription_request.py +2 -2
  26. {monei-2.3.1 → monei-2.3.2}/Monei/model/internal_server_error.py +2 -2
  27. {monei-2.3.1 → monei-2.3.2}/Monei/model/internal_server_error_all_of.py +2 -2
  28. {monei-2.3.1 → monei-2.3.2}/Monei/model/not_found_error.py +2 -2
  29. {monei-2.3.1 → monei-2.3.2}/Monei/model/not_found_error_all_of.py +2 -2
  30. {monei-2.3.1 → monei-2.3.2}/Monei/model/pause_subscription_request.py +2 -2
  31. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment.py +2 -2
  32. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_billing_details.py +2 -2
  33. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_cancellation_reason.py +2 -2
  34. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_customer.py +2 -2
  35. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_last_refund_reason.py +2 -2
  36. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_message_channel.py +2 -2
  37. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_message_language.py +2 -2
  38. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods.py +2 -2
  39. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata.py +2 -2
  40. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_alipay.py +2 -2
  41. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_apple_pay.py +2 -2
  42. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_bancontact.py +2 -2
  43. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_bizum.py +2 -2
  44. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_blik.py +2 -2
  45. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_card.py +2 -2
  46. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_click_to_pay.py +2 -2
  47. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_click_to_pay_discover.py +2 -2
  48. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_click_to_pay_mastercard.py +2 -2
  49. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_click_to_pay_visa.py +2 -2
  50. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_eps.py +2 -2
  51. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_giropay.py +2 -2
  52. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_google_pay.py +2 -2
  53. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_i_deal.py +2 -2
  54. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_klarna.py +2 -2
  55. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_mbway.py +2 -2
  56. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_sepa.py +2 -2
  57. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_sofort.py +2 -2
  58. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_metadata_trustly.py +2 -2
  59. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_methods_methods.py +2 -2
  60. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_next_action.py +4 -4
  61. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method.py +2 -2
  62. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_bizum.py +2 -2
  63. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_bizum_input.py +2 -2
  64. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_card.py +4 -4
  65. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_card_input.py +2 -2
  66. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_cofidis.py +2 -2
  67. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_input.py +2 -2
  68. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_klarna.py +2 -2
  69. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_mbway.py +2 -2
  70. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_paypal.py +2 -2
  71. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_sepa.py +2 -2
  72. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_method_trustly.py +2 -2
  73. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_payment_methods.py +6 -6
  74. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_refund_reason.py +2 -2
  75. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_sequence.py +2 -2
  76. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_sequence_recurring.py +2 -2
  77. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_session_details.py +2 -2
  78. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_shipping_details.py +2 -2
  79. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_shop.py +2 -2
  80. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_status.py +2 -2
  81. {monei-2.3.1 → monei-2.3.2}/Monei/model/payment_trace_details.py +2 -2
  82. monei-2.3.2/Monei/model/payment_transaction_type.py +286 -0
  83. {monei-2.3.1 → monei-2.3.2}/Monei/model/recurring_payment_request.py +4 -4
  84. {monei-2.3.1 → monei-2.3.2}/Monei/model/refund_payment_request.py +2 -2
  85. {monei-2.3.1 → monei-2.3.2}/Monei/model/register_apple_pay_domain_request.py +2 -2
  86. {monei-2.3.1 → monei-2.3.2}/Monei/model/send_payment_link_request.py +2 -2
  87. {monei-2.3.1 → monei-2.3.2}/Monei/model/send_payment_receipt_request.py +2 -2
  88. {monei-2.3.1 → monei-2.3.2}/Monei/model/send_payment_request_request.py +2 -2
  89. {monei-2.3.1 → monei-2.3.2}/Monei/model/send_subscription_link_request.py +2 -2
  90. {monei-2.3.1 → monei-2.3.2}/Monei/model/send_subscription_status_request.py +2 -2
  91. {monei-2.3.1 → monei-2.3.2}/Monei/model/service_unavailable_error.py +2 -2
  92. {monei-2.3.1 → monei-2.3.2}/Monei/model/service_unavailable_error_all_of.py +2 -2
  93. {monei-2.3.1 → monei-2.3.2}/Monei/model/subscription.py +2 -2
  94. {monei-2.3.1 → monei-2.3.2}/Monei/model/subscription_interval.py +2 -2
  95. {monei-2.3.1 → monei-2.3.2}/Monei/model/subscription_last_payment.py +2 -2
  96. {monei-2.3.1 → monei-2.3.2}/Monei/model/subscription_payment_method.py +2 -2
  97. {monei-2.3.1 → monei-2.3.2}/Monei/model/subscription_payment_method_card.py +2 -2
  98. {monei-2.3.1 → monei-2.3.2}/Monei/model/subscription_retry_schedule.py +2 -2
  99. {monei-2.3.1 → monei-2.3.2}/Monei/model/subscription_retry_schedule_inner.py +2 -2
  100. {monei-2.3.1 → monei-2.3.2}/Monei/model/subscription_status.py +2 -2
  101. {monei-2.3.1 → monei-2.3.2}/Monei/model/unauthorized_error.py +2 -2
  102. {monei-2.3.1 → monei-2.3.2}/Monei/model/unauthorized_error_all_of.py +2 -2
  103. {monei-2.3.1 → monei-2.3.2}/Monei/model/unprocessable_entity_error.py +2 -2
  104. {monei-2.3.1 → monei-2.3.2}/Monei/model/unprocessable_entity_error_all_of.py +2 -2
  105. {monei-2.3.1 → monei-2.3.2}/Monei/model/update_subscription_request.py +2 -2
  106. {monei-2.3.1 → monei-2.3.2}/Monei/model/validate_bizum_phone_request.py +2 -2
  107. {monei-2.3.1 → monei-2.3.2}/Monei/model_utils.py +2 -2
  108. {monei-2.3.1 → monei-2.3.2}/Monei/monei_client.py +7 -5
  109. {monei-2.3.1 → monei-2.3.2}/Monei/rest.py +2 -2
  110. {monei-2.3.1 → monei-2.3.2}/PKG-INFO +1 -1
  111. {monei-2.3.1 → monei-2.3.2}/config.json +1 -1
  112. {monei-2.3.1 → monei-2.3.2}/package.json +1 -1
  113. {monei-2.3.1 → monei-2.3.2}/pyproject.toml +1 -1
  114. monei-2.3.2/scripts/post-build.sh +6 -0
  115. {monei-2.3.1 → monei-2.3.2}/uv.lock +1 -1
  116. monei-2.3.1/Monei/__init__.py +0 -30
  117. monei-2.3.1/Monei/model/payment_transaction_type.py +0 -286
  118. monei-2.3.1/scripts/post-build.sh +0 -3
  119. {monei-2.3.1 → monei-2.3.2}/.cursor/rules/general.mdc +0 -0
  120. {monei-2.3.1 → monei-2.3.2}/.gitattributes +0 -0
  121. {monei-2.3.1 → monei-2.3.2}/.github/workflows/deploy.yml +0 -0
  122. {monei-2.3.1 → monei-2.3.2}/.github/workflows/test.yml +0 -0
  123. {monei-2.3.1 → monei-2.3.2}/.gitignore +0 -0
  124. {monei-2.3.1 → monei-2.3.2}/.husky/commit-msg +0 -0
  125. {monei-2.3.1 → monei-2.3.2}/.husky/pre-commit +0 -0
  126. {monei-2.3.1 → monei-2.3.2}/.openapi-generator/FILES +0 -0
  127. {monei-2.3.1 → monei-2.3.2}/.openapi-generator/VERSION +0 -0
  128. {monei-2.3.1 → monei-2.3.2}/.openapi-generator-ignore +0 -0
  129. {monei-2.3.1 → monei-2.3.2}/.release-it.json +0 -0
  130. {monei-2.3.1 → monei-2.3.2}/.uv/uv.toml +0 -0
  131. {monei-2.3.1 → monei-2.3.2}/.yarnrc.yml +0 -0
  132. {monei-2.3.1 → monei-2.3.2}/LICENSE +0 -0
  133. {monei-2.3.1 → monei-2.3.2}/Monei/api/__init__.py +0 -0
  134. {monei-2.3.1 → monei-2.3.2}/Monei/api_response.py +0 -0
  135. {monei-2.3.1 → monei-2.3.2}/Monei/apis/__init__.py +0 -0
  136. {monei-2.3.1 → monei-2.3.2}/Monei/model/__init__.py +0 -0
  137. {monei-2.3.1 → monei-2.3.2}/Monei/model/error_base.py +0 -0
  138. {monei-2.3.1 → monei-2.3.2}/Monei/models/__init__.py +0 -0
  139. {monei-2.3.1 → monei-2.3.2}/Monei/py.typed +0 -0
  140. {monei-2.3.1 → monei-2.3.2}/README.md +0 -0
  141. {monei-2.3.1 → monei-2.3.2}/commitlint.config.js +0 -0
  142. {monei-2.3.1 → monei-2.3.2}/openapitools.json +0 -0
  143. {monei-2.3.1 → monei-2.3.2}/scripts/build.sh +0 -0
  144. {monei-2.3.1 → monei-2.3.2}/scripts/release.sh +0 -0
  145. {monei-2.3.1 → monei-2.3.2}/test/__init__.py +0 -0
  146. {monei-2.3.1 → monei-2.3.2}/test/test_activate_subscription_request.py +0 -0
  147. {monei-2.3.1 → monei-2.3.2}/test/test_address.py +0 -0
  148. {monei-2.3.1 → monei-2.3.2}/test/test_api_client.py +0 -0
  149. {monei-2.3.1 → monei-2.3.2}/test/test_api_exception.py +0 -0
  150. {monei-2.3.1 → monei-2.3.2}/test/test_api_response.py +0 -0
  151. {monei-2.3.1 → monei-2.3.2}/test/test_apple_pay_domain_api.py +0 -0
  152. {monei-2.3.1 → monei-2.3.2}/test/test_apple_pay_domain_api_integration.py +0 -0
  153. {monei-2.3.1 → monei-2.3.2}/test/test_apple_pay_domain_register200_response.py +0 -0
  154. {monei-2.3.1 → monei-2.3.2}/test/test_apple_pay_domain_register400_response.py +0 -0
  155. {monei-2.3.1 → monei-2.3.2}/test/test_apple_pay_domain_register401_response.py +0 -0
  156. {monei-2.3.1 → monei-2.3.2}/test/test_apple_pay_domain_register404_response.py +0 -0
  157. {monei-2.3.1 → monei-2.3.2}/test/test_apple_pay_domain_register422_response.py +0 -0
  158. {monei-2.3.1 → monei-2.3.2}/test/test_apple_pay_domain_register500_response.py +0 -0
  159. {monei-2.3.1 → monei-2.3.2}/test/test_apple_pay_domain_register503_response.py +0 -0
  160. {monei-2.3.1 → monei-2.3.2}/test/test_bad_request_error.py +0 -0
  161. {monei-2.3.1 → monei-2.3.2}/test/test_bad_request_error_all_of.py +0 -0
  162. {monei-2.3.1 → monei-2.3.2}/test/test_bizum_api.py +0 -0
  163. {monei-2.3.1 → monei-2.3.2}/test/test_bizum_api_integration.py +0 -0
  164. {monei-2.3.1 → monei-2.3.2}/test/test_bizum_validate_phone200_response.py +0 -0
  165. {monei-2.3.1 → monei-2.3.2}/test/test_browser_color_depth.py +0 -0
  166. {monei-2.3.1 → monei-2.3.2}/test/test_browser_screen_height.py +0 -0
  167. {monei-2.3.1 → monei-2.3.2}/test/test_browser_screen_width.py +0 -0
  168. {monei-2.3.1 → monei-2.3.2}/test/test_browser_timezone_offset.py +0 -0
  169. {monei-2.3.1 → monei-2.3.2}/test/test_cancel_payment_request.py +0 -0
  170. {monei-2.3.1 → monei-2.3.2}/test/test_cancel_subscription_request.py +0 -0
  171. {monei-2.3.1 → monei-2.3.2}/test/test_capture_payment_request.py +0 -0
  172. {monei-2.3.1 → monei-2.3.2}/test/test_configuration.py +0 -0
  173. {monei-2.3.1 → monei-2.3.2}/test/test_confirm_payment_request.py +0 -0
  174. {monei-2.3.1 → monei-2.3.2}/test/test_confirm_payment_request_payment_method.py +0 -0
  175. {monei-2.3.1 → monei-2.3.2}/test/test_confirm_payment_request_payment_method_card.py +0 -0
  176. {monei-2.3.1 → monei-2.3.2}/test/test_create_payment_request.py +0 -0
  177. {monei-2.3.1 → monei-2.3.2}/test/test_create_subscription_request.py +0 -0
  178. {monei-2.3.1 → monei-2.3.2}/test/test_error.py +0 -0
  179. {monei-2.3.1 → monei-2.3.2}/test/test_error_base.py +0 -0
  180. {monei-2.3.1 → monei-2.3.2}/test/test_error_handling.py +0 -0
  181. {monei-2.3.1 → monei-2.3.2}/test/test_exceptions.py +0 -0
  182. {monei-2.3.1 → monei-2.3.2}/test/test_internal_server_error.py +0 -0
  183. {monei-2.3.1 → monei-2.3.2}/test/test_internal_server_error_all_of.py +0 -0
  184. {monei-2.3.1 → monei-2.3.2}/test/test_model_serialization.py +0 -0
  185. {monei-2.3.1 → monei-2.3.2}/test/test_model_serialization_enhancement.py +0 -0
  186. {monei-2.3.1 → monei-2.3.2}/test/test_model_utils.py +0 -0
  187. {monei-2.3.1 → monei-2.3.2}/test/test_monei_client.py +0 -0
  188. {monei-2.3.1 → monei-2.3.2}/test/test_monei_client_additional.py +0 -0
  189. {monei-2.3.1 → monei-2.3.2}/test/test_monei_client_integration.py +0 -0
  190. {monei-2.3.1 → monei-2.3.2}/test/test_not_found_error.py +0 -0
  191. {monei-2.3.1 → monei-2.3.2}/test/test_not_found_error_all_of.py +0 -0
  192. {monei-2.3.1 → monei-2.3.2}/test/test_pause_subscription_request.py +0 -0
  193. {monei-2.3.1 → monei-2.3.2}/test/test_payment.py +0 -0
  194. {monei-2.3.1 → monei-2.3.2}/test/test_payment_billing_details.py +0 -0
  195. {monei-2.3.1 → monei-2.3.2}/test/test_payment_cancellation_reason.py +0 -0
  196. {monei-2.3.1 → monei-2.3.2}/test/test_payment_customer.py +0 -0
  197. {monei-2.3.1 → monei-2.3.2}/test/test_payment_example.py +0 -0
  198. {monei-2.3.1 → monei-2.3.2}/test/test_payment_last_refund_reason.py +0 -0
  199. {monei-2.3.1 → monei-2.3.2}/test/test_payment_message_channel.py +0 -0
  200. {monei-2.3.1 → monei-2.3.2}/test/test_payment_message_language.py +0 -0
  201. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods.py +0 -0
  202. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_api.py +0 -0
  203. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_api_integration.py +0 -0
  204. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata.py +0 -0
  205. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_alipay.py +0 -0
  206. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_apple_pay.py +0 -0
  207. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_bancontact.py +0 -0
  208. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_bizum.py +0 -0
  209. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_blik.py +0 -0
  210. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_card.py +0 -0
  211. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_click_to_pay.py +0 -0
  212. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_click_to_pay_discover.py +0 -0
  213. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_click_to_pay_mastercard.py +0 -0
  214. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_click_to_pay_visa.py +0 -0
  215. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_eps.py +0 -0
  216. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_giropay.py +0 -0
  217. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_google_pay.py +0 -0
  218. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_i_deal.py +0 -0
  219. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_klarna.py +0 -0
  220. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_mbway.py +0 -0
  221. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_sepa.py +0 -0
  222. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_sofort.py +0 -0
  223. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_metadata_trustly.py +0 -0
  224. {monei-2.3.1 → monei-2.3.2}/test/test_payment_methods_methods.py +0 -0
  225. {monei-2.3.1 → monei-2.3.2}/test/test_payment_next_action.py +0 -0
  226. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method.py +0 -0
  227. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_bizum.py +0 -0
  228. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_bizum_input.py +0 -0
  229. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_card.py +0 -0
  230. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_card_input.py +0 -0
  231. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_cofidis.py +0 -0
  232. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_input.py +0 -0
  233. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_klarna.py +0 -0
  234. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_mbway.py +0 -0
  235. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_paypal.py +0 -0
  236. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_sepa.py +0 -0
  237. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_method_trustly.py +0 -0
  238. {monei-2.3.1 → monei-2.3.2}/test/test_payment_payment_methods.py +0 -0
  239. {monei-2.3.1 → monei-2.3.2}/test/test_payment_refund_reason.py +0 -0
  240. {monei-2.3.1 → monei-2.3.2}/test/test_payment_sequence.py +0 -0
  241. {monei-2.3.1 → monei-2.3.2}/test/test_payment_sequence_recurring.py +0 -0
  242. {monei-2.3.1 → monei-2.3.2}/test/test_payment_session_details.py +0 -0
  243. {monei-2.3.1 → monei-2.3.2}/test/test_payment_shipping_details.py +0 -0
  244. {monei-2.3.1 → monei-2.3.2}/test/test_payment_shop.py +0 -0
  245. {monei-2.3.1 → monei-2.3.2}/test/test_payment_status.py +0 -0
  246. {monei-2.3.1 → monei-2.3.2}/test/test_payment_trace_details.py +0 -0
  247. {monei-2.3.1 → monei-2.3.2}/test/test_payment_transaction_type.py +0 -0
  248. {monei-2.3.1 → monei-2.3.2}/test/test_payments_api.py +0 -0
  249. {monei-2.3.1 → monei-2.3.2}/test/test_payments_api_enhancement.py +0 -0
  250. {monei-2.3.1 → monei-2.3.2}/test/test_payments_api_example.py +0 -0
  251. {monei-2.3.1 → monei-2.3.2}/test/test_payments_api_integration.py +0 -0
  252. {monei-2.3.1 → monei-2.3.2}/test/test_recurring_payment_request.py +0 -0
  253. {monei-2.3.1 → monei-2.3.2}/test/test_refund_payment_request.py +0 -0
  254. {monei-2.3.1 → monei-2.3.2}/test/test_register_apple_pay_domain_request.py +0 -0
  255. {monei-2.3.1 → monei-2.3.2}/test/test_rest_enhancement.py +0 -0
  256. {monei-2.3.1 → monei-2.3.2}/test/test_rest_example.py +0 -0
  257. {monei-2.3.1 → monei-2.3.2}/test/test_send_payment_link_request.py +0 -0
  258. {monei-2.3.1 → monei-2.3.2}/test/test_send_payment_receipt_request.py +0 -0
  259. {monei-2.3.1 → monei-2.3.2}/test/test_send_payment_request_request.py +0 -0
  260. {monei-2.3.1 → monei-2.3.2}/test/test_send_subscription_link_request.py +0 -0
  261. {monei-2.3.1 → monei-2.3.2}/test/test_send_subscription_status_request.py +0 -0
  262. {monei-2.3.1 → monei-2.3.2}/test/test_service_unavailable_error.py +0 -0
  263. {monei-2.3.1 → monei-2.3.2}/test/test_service_unavailable_error_all_of.py +0 -0
  264. {monei-2.3.1 → monei-2.3.2}/test/test_subscription.py +0 -0
  265. {monei-2.3.1 → monei-2.3.2}/test/test_subscription_interval.py +0 -0
  266. {monei-2.3.1 → monei-2.3.2}/test/test_subscription_last_payment.py +0 -0
  267. {monei-2.3.1 → monei-2.3.2}/test/test_subscription_payment_method.py +0 -0
  268. {monei-2.3.1 → monei-2.3.2}/test/test_subscription_payment_method_card.py +0 -0
  269. {monei-2.3.1 → monei-2.3.2}/test/test_subscription_retry_schedule.py +0 -0
  270. {monei-2.3.1 → monei-2.3.2}/test/test_subscription_retry_schedule_inner.py +0 -0
  271. {monei-2.3.1 → monei-2.3.2}/test/test_subscription_status.py +0 -0
  272. {monei-2.3.1 → monei-2.3.2}/test/test_subscriptions_api.py +0 -0
  273. {monei-2.3.1 → monei-2.3.2}/test/test_subscriptions_api_enhancement.py +0 -0
  274. {monei-2.3.1 → monei-2.3.2}/test/test_subscriptions_api_integration.py +0 -0
  275. {monei-2.3.1 → monei-2.3.2}/test/test_unauthorized_error.py +0 -0
  276. {monei-2.3.1 → monei-2.3.2}/test/test_unauthorized_error_all_of.py +0 -0
  277. {monei-2.3.1 → monei-2.3.2}/test/test_unprocessable_entity_error.py +0 -0
  278. {monei-2.3.1 → monei-2.3.2}/test/test_unprocessable_entity_error_all_of.py +0 -0
  279. {monei-2.3.1 → monei-2.3.2}/test/test_update_subscription_request.py +0 -0
  280. {monei-2.3.1 → monei-2.3.2}/test/test_validate_bizum_phone_request.py +0 -0
  281. {monei-2.3.1 → monei-2.3.2}/yarn.lock +0 -0
@@ -1,5 +1,9 @@
1
1
  # Changelog
2
2
 
3
+ ## <small>2.3.2 (2025-04-16)</small>
4
+
5
+ * chore: update SDK to OpenAPI specification version 1.6.1 ([9a649be](https://github.com/MONEI/monei-python-sdk/commit/9a649be))
6
+
3
7
  ## <small>2.3.1 (2025-03-14)</small>
4
8
 
5
9
  * chore: update SDK to OpenAPI specification version 1.6.0 ([f1214e5](https://github.com/MONEI/monei-python-sdk/commit/f1214e5))
@@ -0,0 +1,33 @@
1
+ # flake8: noqa
2
+
3
+ """
4
+ MONEI API v1
5
+
6
+ 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. # noqa: E501
7
+
8
+ The version of the OpenAPI document: 1.6.1
9
+ Generated by: https://openapi-generator.tech
10
+ """
11
+
12
+
13
+ __version__ = "2.0.2"
14
+
15
+ # import ApiClient
16
+ from Monei.api_client import ApiClient
17
+
18
+ # import Configuration
19
+ from Monei.configuration import Configuration
20
+
21
+ # import exceptions
22
+ from Monei.exceptions import OpenApiException
23
+ from Monei.exceptions import ApiAttributeError
24
+ from Monei.exceptions import ApiTypeError
25
+ from Monei.exceptions import ApiValueError
26
+ from Monei.exceptions import ApiKeyError
27
+ from Monei.exceptions import ApiException
28
+
29
+ # import custom MoneiClient
30
+ from Monei.monei_client import MoneiClient
31
+ from Monei.models import *
32
+ from Monei.apis import *
33
+ from Monei.exceptions import *
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -604,7 +604,7 @@ class PaymentsApi(object):
604
604
  def confirm(self, id, **kwargs):
605
605
  """Confirm Payment # noqa: E501
606
606
 
607
- Confirms a payment that was created without payment details. This endpoint can only be used with payments in `PENDING` status. The two-step payment flow: 1. **Create**: First, create a payment without payment details (status: `PENDING`) 2. **Confirm**: Then provide payment details to complete the transaction When confirming a payment, you can use: - A newly generated `paymentToken` from [monei.js Components](https://docs.monei.com/docs/monei-js-overview) - A permanent `paymentToken` from a previous payment (generated with `generatePaymentToken: true`) Using permanent payment tokens enables one-click checkout experiences for returning customers without requiring them to re-enter their payment information. You can provide additional customer information during confirmation, which will override any corresponding information originally passed in the payment creation request. # noqa: E501
607
+ Confirms a payment that was created without payment details. This endpoint can only be used with payments in `PENDING` status. The two-step payment flow: 1. **Create**: First, create a payment without payment details (status: `PENDING`) 2. **Confirm**: Then provide payment details to complete the transaction When confirming a payment, you can use: - A newly generated `paymentToken` from [monei.js Components](https://docs.monei.com/monei-js/overview/) - A permanent `paymentToken` from a previous payment (generated with `generatePaymentToken: true`) Using permanent payment tokens enables one-click checkout experiences for returning customers without requiring them to re-enter their payment information. You can provide additional customer information during confirmation, which will override any corresponding information originally passed in the payment creation request. # noqa: E501
608
608
  This method makes a synchronous HTTP request by default. To make an
609
609
  asynchronous HTTP request, please pass async_req=True
610
610
 
@@ -668,7 +668,7 @@ class PaymentsApi(object):
668
668
  def create(self, create_payment_request, **kwargs):
669
669
  """Create Payment # noqa: E501
670
670
 
671
- Creates a new payment with the specified parameters. You can create a payment in two ways: 1. **Immediate processing**: Provide a `paymentToken` or `paymentMethod` - The payment will be processed instantly 2. **Deferred processing**: Create without payment details - The payment remains in `PENDING` status until you confirm it later using the [confirm endpoint](#operation/payments_confirm) When creating a payment without payment details, you can redirect customers to the hosted payment page where they can select their preferred payment method and complete the transaction. For immediate processing, use one of these token options: - A temporary `paymentToken` generated on the frontend using [monei.js Components](https://docs.monei.com/docs/monei-js-overview) - A permanent `paymentToken` from a previous successful payment (when `generatePaymentToken: true` was included) Permanent tokens enable one-click checkout experiences for returning customers by allowing you to securely store and reuse payment details without requiring customers to re-enter their information. # noqa: E501
671
+ Creates a new payment with the specified parameters. You can create a payment in two ways: 1. **Immediate processing**: Provide a `paymentToken` or `paymentMethod` - The payment will be processed instantly 2. **Deferred processing**: Create without payment details - The payment remains in `PENDING` status until you confirm it later using the [confirm endpoint](#operation/payments_confirm) When creating a payment without payment details, you can redirect customers to the hosted payment page where they can select their preferred payment method and complete the transaction. For immediate processing, use one of these token options: - A temporary `paymentToken` generated on the frontend using [monei.js Components](https://docs.monei.com/monei-js/overview/) - A permanent `paymentToken` from a previous successful payment (when `generatePaymentToken: true` was included) Permanent tokens enable one-click checkout experiences for returning customers by allowing you to securely store and reuse payment details without requiring customers to re-enter their information. # noqa: E501
672
672
  This method makes a synchronous HTTP request by default. To make an
673
673
  asynchronous HTTP request, please pass async_req=True
674
674
 
@@ -794,7 +794,7 @@ class PaymentsApi(object):
794
794
  def recurring(self, sequence_id, **kwargs):
795
795
  """Recurring Payment # noqa: E501
796
796
 
797
- Creates a subsequent charge using the payment details from a previous transaction. This endpoint enables recurring billing and subscription payments by: - Using the same payment method as the original payment - Charging the customer without requiring them to re-enter payment details - Supporting variable or fixed amounts (defaults to the original payment amount if not specified) **Prerequisites:** 1. The initial payment must be created with the `sequence` parameter 2. The initial payment will return a `sequenceId` in the response 3. This `sequenceId` must be provided in the URL path when making subsequent recurring charges Ideal for subscription services, membership renewals, and installment payments. **Need more advanced subscription management?** For comprehensive subscription management with features like billing cycles, trial periods, and automatic recurring billing, consider using the [Subscriptions API](#tag/Subscriptions) instead. It provides a complete solution for creating and managing subscription-based services. # noqa: E501
797
+ Creates a subsequent charge using the payment details from a previous transaction. This endpoint enables recurring billing and subscription payments by: - Using the same payment method as the original payment - Charging the customer without requiring them to re-enter payment details - Supporting variable or fixed amounts (defaults to the original payment amount if not specified) **Prerequisites:** 1. The initial payment must be created with the `sequence` parameter 2. The initial payment will return a `sequenceId` in the response 3. This `sequenceId` must be provided in the URL path when making subsequent recurring charges Ideal for subscription services, membership renewals, and installment payments. **Need more advanced subscription management?** For comprehensive subscription management with features like billing cycles, trial periods, and automatic recurring billing, consider using the [Subscriptions API](https://docs.monei.com/apis/rest/subscriptions/) instead. It provides a complete solution for creating and managing subscription-based services. # noqa: E501
798
798
  This method makes a synchronous HTTP request by default. To make an
799
799
  asynchronous HTTP request, please pass async_req=True
800
800
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -431,7 +431,7 @@ class Configuration(object):
431
431
  "Python SDK Debug Report:\n"
432
432
  "OS: {env}\n"
433
433
  "Python Version: {pyversion}\n"
434
- "Version of the API: 1.6.0\n"
434
+ "Version of the API: 1.6.1\n"
435
435
  "SDK Package Version: 2.0.2".format(env=sys.platform, pyversion=sys.version)
436
436
  )
437
437
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -174,7 +174,7 @@ class ActivateSubscriptionRequest(ModelNormal):
174
174
  Animal class but this time we won't travel
175
175
  through its discriminator because we passed in
176
176
  _visited_composed_classes = (Animal,)
177
- payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/docs/monei-js-overview) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/docs/save-payment-method). In case of the first one, you will also need to send the `sessionId` used to generate the token in the first place. . [optional] # noqa: E501
177
+ payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/monei-js/overview/) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/guides/save-payment-method/). In case of the first one, you will also need to send the `sessionId` used to generate the token in the first place. . [optional] # noqa: E501
178
178
  session_id (str): A unique identifier within your system that adds security to the payment process. You need to pass the same session ID as the one used on the frontend to initialize MONEI Component (if you needed to). This is required if a payment token (not permanent) was already generated in the frontend. . [optional] # noqa: E501
179
179
  add_amount (bool, date, datetime, dict, float, int, list, str, none_type): The amount to be added to the subscription's initial payment. A positive integer representing how much to charge in the smallest currency unit (e.g., 100 cents to charge 1.00 USD). . [optional] # noqa: E501
180
180
  sequence_id (str): A permanent identifier that refers to the initial payment of a sequence of payments. This value needs to be sent in the path for `RECURRING` payments. . [optional] # noqa: E501
@@ -272,7 +272,7 @@ class ActivateSubscriptionRequest(ModelNormal):
272
272
  Animal class but this time we won't travel
273
273
  through its discriminator because we passed in
274
274
  _visited_composed_classes = (Animal,)
275
- payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/docs/monei-js-overview) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/docs/save-payment-method). In case of the first one, you will also need to send the `sessionId` used to generate the token in the first place. . [optional] # noqa: E501
275
+ payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/monei-js/overview/) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/guides/save-payment-method/). In case of the first one, you will also need to send the `sessionId` used to generate the token in the first place. . [optional] # noqa: E501
276
276
  session_id (str): A unique identifier within your system that adds security to the payment process. You need to pass the same session ID as the one used on the frontend to initialize MONEI Component (if you needed to). This is required if a payment token (not permanent) was already generated in the frontend. . [optional] # noqa: E501
277
277
  add_amount (bool, date, datetime, dict, float, int, list, str, none_type): The amount to be added to the subscription's initial payment. A positive integer representing how much to charge in the smallest currency unit (e.g., 100 cents to charge 1.00 USD). . [optional] # noqa: E501
278
278
  sequence_id (str): A permanent identifier that refers to the initial payment of a sequence of payments. This value needs to be sent in the path for `RECURRING` payments. . [optional] # noqa: E501
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -148,7 +148,7 @@ class ConfirmPaymentRequest(ModelNormal):
148
148
  """ConfirmPaymentRequest - a model defined in OpenAPI
149
149
 
150
150
  Args:
151
- payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/docs/monei-js-overview) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/docs/save-payment-method).
151
+ payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/monei-js/overview/) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/guides/save-payment-method/).
152
152
 
153
153
  Keyword Args:
154
154
  _check_type (bool): if True, values for parameters in openapi_types
@@ -248,7 +248,7 @@ class ConfirmPaymentRequest(ModelNormal):
248
248
  """ConfirmPaymentRequest - a model defined in OpenAPI
249
249
 
250
250
  Args:
251
- payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/docs/monei-js-overview) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/docs/save-payment-method).
251
+ payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/monei-js/overview/) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/guides/save-payment-method/).
252
252
 
253
253
  Keyword Args:
254
254
  _check_type (bool): if True, values for parameters in openapi_types
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -1,9 +1,9 @@
1
1
  """
2
2
  MONEI API v1
3
3
 
4
- The MONEI API is organized around [REST](https://en.wikipedia.org/wiki/Representational_State_Transfer) 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. # Authentication <!-- Redoc-Inject: <security-definitions> --> # noqa: E501
4
+ 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. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: 1.6.0
6
+ The version of the OpenAPI document: 1.6.1
7
7
  Generated by: https://openapi-generator.tech
8
8
  """
9
9
 
@@ -231,7 +231,7 @@ class CreatePaymentRequest(ModelNormal):
231
231
  complete_url (str): The URL the customer will be directed to after transaction completed (successful or failed - except if `failUrl` is provided). . [optional] # noqa: E501
232
232
  fail_url (str): The URL the customer will be directed to after transaction has failed, instead of `completeUrl` (used in hosted payment page). This allows to provide two different URLs for successful and failed payments. . [optional] # noqa: E501
233
233
  cancel_url (str): The URL the customer will be directed to if they decide to cancel payment and return to your website (used in hosted payment page). . [optional] # noqa: E501
234
- payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/docs/monei-js-overview) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/docs/save-payment-method). In case of the first one, you will also need to send the `sessionId` used to generate the token in the first place. . [optional] # noqa: E501
234
+ payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/monei-js/overview/) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/guides/save-payment-method/). In case of the first one, you will also need to send the `sessionId` used to generate the token in the first place. . [optional] # noqa: E501
235
235
  session_id (str): A unique identifier within your system that adds security to the payment process. You need to pass the same session ID as the one used on the frontend to initialize MONEI Component (if you needed to). This is required if a payment token (not permanent) was already generated in the frontend. . [optional] # noqa: E501
236
236
  generate_payment_token (bool): If set to true a permanent token that represents a payment method used in the payment will be generated. . [optional] if omitted the server will use the default value of False # noqa: E501
237
237
  payment_method (PaymentPaymentMethodInput): [optional] # noqa: E501
@@ -351,7 +351,7 @@ class CreatePaymentRequest(ModelNormal):
351
351
  complete_url (str): The URL the customer will be directed to after transaction completed (successful or failed - except if `failUrl` is provided). . [optional] # noqa: E501
352
352
  fail_url (str): The URL the customer will be directed to after transaction has failed, instead of `completeUrl` (used in hosted payment page). This allows to provide two different URLs for successful and failed payments. . [optional] # noqa: E501
353
353
  cancel_url (str): The URL the customer will be directed to if they decide to cancel payment and return to your website (used in hosted payment page). . [optional] # noqa: E501
354
- payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/docs/monei-js-overview) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/docs/save-payment-method). In case of the first one, you will also need to send the `sessionId` used to generate the token in the first place. . [optional] # noqa: E501
354
+ payment_token (bool, date, datetime, dict, float, int, list, str, none_type): A payment token generated by monei.js [Components](https://docs.monei.com/monei-js/overview/) or a paymentToken [saved after a previous successful payment](https://docs.monei.com/guides/save-payment-method/). In case of the first one, you will also need to send the `sessionId` used to generate the token in the first place. . [optional] # noqa: E501
355
355
  session_id (str): A unique identifier within your system that adds security to the payment process. You need to pass the same session ID as the one used on the frontend to initialize MONEI Component (if you needed to). This is required if a payment token (not permanent) was already generated in the frontend. . [optional] # noqa: E501
356
356
  generate_payment_token (bool): If set to true a permanent token that represents a payment method used in the payment will be generated. . [optional] if omitted the server will use the default value of False # noqa: E501
357
357
  payment_method (PaymentPaymentMethodInput): [optional] # noqa: E501