rust/hyperswitch
1
0
Fork 0
mirror of https://github.com/juspay/hyperswitch.git synced 2025-10-29 00:49:42 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat(core): store customer_acceptance in the payment_methods table (#3885)

Browse Source
This commit is contained in:
Amisha Prabhat
2024-03-06 15:00:16 +05:30
committed by GitHub
parent 289b20a82e
commit a1fd36a1ab
83 changed files with 575 additions and 127 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
crates/api_models/src/payments.rs
View File

@ -348,9 +348,12 @@ pub struct PaymentsRequest {
#[remove_in(PaymentsUpdateRequest, PaymentsCreateRequest)]
pub client_secret: Option<String>,
/// Passing this object during payments creates a mandate. The mandate_type sub object is passed by the server usually and the customer_acceptance sub object is usually passed by the SDK or client
/// Passing this object during payments creates a mandate. The mandate_type sub object is passed by the server.
pub mandate_data: Option<MandateData>,
/// Passing this object during payments confirm . The customer_acceptance sub object is usually passed by the SDK or client
pub customer_acceptance: Option<CustomerAcceptance>,
/// A unique identifier to link the payment to a mandate. To do Recurring payments after a mandate has been created, pass the mandate_id instead of payment_method_data
#[schema(max_length = 255, example = "mandate_iwer89rnjef349dni3")]
#[remove_in(PaymentsUpdateRequest)]