API Error Codes Reference

Auto-generated. Do not edit manually.

Agent Object Error Codes

Location

See details

Error Code Summary

Error Category	Error Title Reference	Error Title	HTTP Status	Error Message
CCG Schema Validation	First Name Validation	INVALID_REQUEST	400 BAD REQUEST	agent.firstName cannot be more than 50 characters
CCG Schema Validation	Last Name Validation	INVALID_REQUEST	400 BAD REQUEST	agent.lastName cannot be more than 50 characters
CCG Schema Validation	User ID Validation	INVALID_REQUEST	400 BAD REQUEST	agent.userId is required

Consent Object Error Codes

Location

See details

Error Code Summary

Error Category	Error Title Reference	Error Title	HTTP Status	Error Message
CCG Schema Validation	Merchant Consent Text Validation	INVALID_REQUEST	400 BAD_REQUEST	Consent is Invalid!
CCG Schema Validation	Merchant Consent Id Validation	INVALID_REQUEST	400 BAD_REQUEST	merchantConsentId is required
CCG Schema Validation	Consent Collection Timestamp Validation	INVALID_REQUEST	400 BAD_REQUEST	collectionTimestamp is required
CCG Schema Validation	Consent Collection Details Validation	INVALID_REQUEST	400 BAD_REQUEST	collectionDetails are not valid
CCG Schema Validation	Agent Object Requirement with PPD Consent	INVALID_REQUEST	400 BAD_REQUEST	agent object is required with PPD consent

Customer Object Error Codes

Location

See details

Error Code Summary

Error Category	Error Title Reference	Error Title	HTTP Status	Error Message
CCG Schema Validation	Missing Required Identifiers	INVALID_REQUEST	400 BAD REQUEST	customer should contain hsid, enterpriseId or metadata
CCG Schema Validation	Invalid Enterprise ID	INVALID_REQUEST	400 BAD REQUEST	customer.enterpriseId is invalid
CCG Schema Validation	Invalid HSID	INVALID_REQUEST	400 BAD REQUEST	customer.hsid must be a valid UUID
CCG Schema Validation	Customer Not Found	NOT_FOUND	404 NOT FOUND	Customer not found for given enterpriseId
CCG Schema Validation	Exceeded Metadata Entries	INVALID_REQUEST	400 BAD REQUEST	customer.metadata maximum allowed number of entries is 20
CCG Schema Validation	Metadata Key Size Exceeded	INVALID_REQUEST	400 BAD REQUEST	customer.metadata key maximum allowed length is 40
CCG Schema Validation	Metadata Value Size Exceeded	INVALID_REQUEST	400 BAD REQUEST	customer.metadata value maximum allowed length is 100
CCG Schema Validation	Email Validation	INVALID_REQUEST	400 BAD REQUEST	customer.email must be a valid email address
CCG Schema Validation	First Name Length Exceeded	INVALID_REQUEST	400 BAD REQUEST	First name max length is 100
CCG Schema Validation	Last Name Length Exceeded	INVALID_REQUEST	400 BAD REQUEST	Last name max length is 100
CCG Schema Validation	SSN Validation	INVALID_REQUEST	400 BAD REQUEST	customer.ssnLastFour must be 4 digits

Payment Details Object Error Codes

Location

See details

Error Code Summary

Error Category	Error Title Reference	Error Title	HTTP Status	Error Message
CCG Schema Validation	Payment Details Validation	INVALID_REQUEST	400 BAD REQUEST	payment details are not valid
CCG Schema Validation	Qualified + Vision Amount Exceeds Total Amount	INVALID_REQUEST	400 BAD REQUEST	details qualified amount + vision amount cannot be greater than amount
CCG Schema Validation	Prescription Amount Exceeds Qualified Amount	INVALID_REQUEST	400 BAD REQUEST	details prescription amount cannot be greater than qualified amount

Payment Object Error Codes

Location

See details

Error Code Summary

Error Category	Error Title Reference	Error Title	HTTP Status	Error Message
CCG Schema Validation	Partial Authorization Not Allowed	INVALID_REQUEST	400 BAD REQUEST	Partial authorization not allowed for authorizeCard = false
CCG Schema Validation	Statement Descriptor Suffix Invalid	INVALID_REQUEST	400 BAD REQUEST	payment.statementDescriptorSuffix only allows alphanumeric, space, hyphen and dot with at least one letter and allowed maximum length is 10
CCG Schema Validation	Invalid Amount	INVALID_REQUEST	400 BAD REQUEST	Invalid amount ${validatedValue}, it must be between 1 and 99999999 and not contain decimals
CCG Schema Validation	Exceeded Metadata Entries	INVALID_REQUEST	400 BAD REQUEST	metadata maximum allowed number of entries is 20
CCG Schema Validation	Metadata Key Size Exceeded	INVALID_REQUEST	400 BAD REQUEST	metadata key maximum allowed length is 40
CCG Schema Validation	Metadata Value Size Exceeded	INVALID_REQUEST	400 BAD REQUEST	metadata value maximum allowed length is 100
CCG Schema Validation	Description Size Exceeded	INVALID_REQUEST	400 BAD REQUEST	description maximum allowed length is 100
CCG Schema Validation	Merchant Transaction ID Required	INVALID_REQUEST	400 BAD REQUEST	merchantTransactionId is required
CCG Schema Validation	Merchant Transaction ID Too Long	INVALID_REQUEST	400 BAD REQUEST	merchantTransactionId maximum allowed length is 50
CCG Schema Validation	Missing Payment Allocations	INVALID_REQUEST	400 BAD REQUEST	paymentAllocations is required.
CCG Schema Validation	Too Many Payment Allocations	INVALID_REQUEST	400 BAD REQUEST	Maximum number of allocations allowed is 2
CCG Schema Validation	Invalid Allocation Amount	INVALID_REQUEST	400 BAD REQUEST	paymentAllocations[0].amount 0.1 is invalid, it must be between 1 and 99999999 and not contain decimals.
CCG Schema Validation	Missing Payment Amount	INVALID_REQUEST	400 BAD REQUEST	amount is required
CCG Schema Validation	Missing Allocation Amount	INVALID_REQUEST	400 BAD REQUEST	paymentAllocations[0].amount is required
CCG Schema Validation	Allocation Sum Mismatch	INVALID_REQUEST	400 BAD REQUEST	sum of paymentAllocations[:].amount should be equal to payment.amount
CCG Schema Validation	Duplicate Payment Method Id	INVALID_REQUEST	400 BAD REQUEST	paymentAllocations[:].paymentMethodId cannot be same
CCG Schema Validation	Missing Payment Method Id	INVALID_REQUEST	400 BAD REQUEST	paymentAllocations[:].paymentMethodId is required
CCG Schema Validation	Invalid Payment Method Id	INVALID_REQUEST	400 BAD REQUEST	paymentAllocations[n].paymentMethodId is invalid

Cancel Payments API Error Codes

Location

See details

Error Code Summary

Error Title Reference	Error Title	HTTP Status	Detail Message
Payment Cancellation Reason Missing	INVALID_REQUEST	400 BAD REQUEST	paymentCancellationReason is missing or null
Invalid Payment Cancellation Reason	INVALID_REQUEST	400 BAD REQUEST	Invalid paymentCancellationReason

Payment Error Codes

Location

See details

Error Code Summary

Error Category	Error Title Reference	Error Title	HTTP Status	Error Message
CCG Schema Validation	Consent Requirement	INVALID_REQUEST	400 BAD REQUEST	Consent is required!
CCG Business Validation	Payment Method Not Found	PAYMENT_METHOD_ERROR	406 NOT_ACCEPTABLE	Payment method ending with {last4} is not found. Please provide a valid payment method.
CCG Business Validation	Payment Method Type Not Configured	PAYMENT_METHOD_ERROR	406 NOT_ACCEPTABLE	Payment method ending with {last4} is not configured. Please provide a valid payment method.
CCG Business Validation	Invalid Payment Methods	PAYMENT_METHOD_ERROR	406 NOT_ACCEPTABLE	Payment method ending with {last4} is or invalid. Please provide a valid payment method.
Payment Processor Validation	Vendor Processing Error	PAYMENT_METHOD_ERROR	406 NOT_ACCEPTABLE	One of the split tender card payments failed during processing.
CCG Business Validation	Card Requires 3D Secure Authentication	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	This card requires an additional security step to be performed by the customer. Please have the customer enter the card via text or email; otherwise, have the customer provide a different payment method.
CCG Business Validation	Payment Method Requires Authentication	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	Payment method could not be authorized. This payment method requires authentication from a customer.

Stripe Payment Processing Error Codes

Location

See details

Error Code Summary

Error Category	Error Title Reference	Error Title	HTTP Status	Error Message
Payment Processor Validation	Card Authentication Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	This card requires an additional security step to be performed by the customer. Please have the customer enter the card via text or email; otherwise, have the customer provide a different payment method.
Payment Processor Validation	Card Authentication Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	Payment method could not be authorized. This payment method requires authentication from a customer.
Payment Processor Validation	Card Decline Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	The card was declined for an unknown reason. Contact issuer for more information.
Payment Processor Validation	Card Decline Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	An error occurred while processing the card, please try again.
Payment Processor Validation	Card Decline Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	Payment method could not be authorized. Please try a different payment method.
Payment Processor Validation	Card Decline Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	Payment method is canceled by a customer or expired by the financial partner
Payment Processor Validation	Card Validation Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	The CVC number is incorrect.
Payment Processor Validation	Card Validation Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	The card has expired.
Payment Processor Validation	Financial Limit Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	The customer's account has insufficient funds to complete the purchase. Please use an alternative payment method.
Payment Processor Validation	Financial Limit Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	The customer has exceeded the balance, credit limit, or transaction amount limit available on their card. Contact issuer for more information.
Payment Processor Validation	Bank Account Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	The customer's bank account has been closed.
Payment Processor Validation	Bank Account Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	The customer's bank account could not be located.
Payment Processor Validation	Early Warning System Errors	PAYMENT_METHOD_ERROR	406 NOT ACCEPTABLE	earlyWarningMessage

Refund API Error Codes

Location

See details

Error Code Summary

Error Title Reference	Error Title	HTTP Status	Detail Message	Scenario	Resolution
Structural Validation Errors	BAD_REQUEST	400 BAD REQUEST	MerchantTransactionId must be unique across all refund requests.	Duplicate merchantTransactionId provided.	Use a new merchantTransactionId for each refund request.
Structural Validation Errors	BAD_REQUEST	400 BAD_REQUEST	Refund already exists for the given merchantTransactionId.	A refund with the same merchantTransactionId already exists.	Do not retry with the same transaction ID; generate a new one.
Structural Validation Errors	BAD_REQUEST	400 BAD REQUEST	merchantTransactionId is required.	merchantTransactionId missing in the request.	Provide a valid merchantTransactionId field.
Structural Validation Errors	BAD_REQUEST	400 BAD REQUEST	reason is required.	reason field missing from the request.	Include reason and ensure it has a valid value.
Structural Validation Errors	BAD_REQUEST	400 BAD REQUEST	Invalid refund reason. reason can have only allowed values.	Provided reason is not part of the allowed enum.	Use only documented enum values for reason.
Structural Validation Errors	BAD_REQUEST	400 BAD REQUEST	paymentId is required.	paymentId missing from the request.	Provide a valid paymentId from a previous payment.
Structural Validation Errors	BAD_REQUEST	400 BAD REQUEST	payment not found.	paymentId not found or not associated with the merchant.	Use a valid paymentId from a Create Payment response.
Structural Validation Errors	BAD_REQUEST	400 BAD REQUEST	paymentAllocationId not linked to paymentId	refundAllocations contains IDs not belonging to the referenced payment.	Use paymentAllocationIds belonging to the correct payment.
Structural Validation Errors	BAD_REQUEST	400 BAD REQUEST	amount is required for each refundAllocations.	Missing amount in a refundAllocations entry.	Add an amount value to every refundAllocations entry.
Structural Validation Errors	BAD_REQUEST	400 BAD REQUEST	paymentAllocationId is required for each refundAllocations.	Missing paymentAllocationId in refundAllocations.	Provide a valid paymentAllocationId for each entry.
Structural Validation Errors	BAD_REQUEST	400 BAD_REQUEST	Zero-amount refunds not allowed.	amount = 0 submitted.	Submit only positive refund amounts.

Error Title Reference	Error Title	HTTP Status	Detail Message	Scenario	Resolution
Structural Validation Errors	NOT_FOUND	404 NOT_FOUND	Refund information not found.	refundId not found in CCG, or refundId not associated with the requesting merchant.	Use a valid refundId returned from Create Refund, and ensure the refund belongs to the requesting merchant.
Structural Validation Errors	BAD_REQUEST	400 BAD_REQUEST	RefundId is invalid.	refundId is not in valid UUID format.	Provide a valid UUID-formatted refundId.

Refund Error Codes

Location

See details

Error Code Summary

Error Title Reference	Error Title	HTTP Status	Detail Message	Scenario	Resolution
Refund Amount Validation	INVALID_REQUEST	400 BAD REQUEST	Refund amount cannot be more than the un-refunded amount of the original payment	When attempting to refund more than the available amount	Ensure refund amount is less than or equal to the available (un-refunded) amount
	INVALID_REQUEST	400 BAD REQUEST	When paymentMethodId is present, amount is required	When using paymentMethodId without specifying an amount	Include a valid amount when using paymentMethodId
Payment Status Validation	PAYMENT_ERROR	400 BAD REQUEST	Cannot issue refund for this payment	When attempting to refund a payment not in COMPLETED status	Only attempt to refund payments that are in COMPLETED status
Payment Status Validation	INVALID_REQUEST	400 BAD REQUEST	Cannot issue refund for this payment	When attempting to refund for disputed fraudulent transaction	Disputed fraudulent transactions cannot be refunded
	INVALID_REQUEST	400 BAD REQUEST	Refunds can only be processed for captured payments	When attempting to refund a payment in AUTHORIZED status	Capture the payment before attempting to refund it or cancel the payment if not required.
	INVALID_REQUEST	400 BAD REQUEST	The amount given exceeds the allowed refund limit	When attempting to issue Credit beyond allowed refund limit	Reduce the refund amount to be within the allowed limit
Payment Identifier Validation	INVALID_REQUEST	400 BAD REQUEST	paymentId or paymentMethodId is required	When neither paymentId nor paymentMethodId is provided	Include either paymentId or paymentMethodId in the request
	INVALID_REQUEST	400 BAD REQUEST	Either paymentId or paymentMethodId should be provided. The request has both paymentId and paymentMethodId	When both paymentId and paymentMethodId are provided	Use either paymentId or paymentMethodId, not both
	INVALID_REQUEST	400 BAD REQUEST	When paymentMethodId is present, customer should contain hsid, enterpriseId or metadata	When customer identifiers are missing with paymentMethodId	Include customer identifiers when using paymentMethodId
Payment Method Status Validation	INVALID_REQUEST	400 BAD REQUEST	Payment method is canceled by a customer or expired by the financial partner	When attempting to refund using an invalid payment method	Use only valid, active payment methods for refunds
	INVALID_REQUEST	400 BAD REQUEST	Credit is not allowed for bank accounts.	When attempting to refund to a bank account payment method	Use card payment methods for unlinked refunds/credits
	INVALID_REQUEST	400 BAD REQUEST	Invalid paymentMethodId	When attempting to issue Credit for Invalid or Deleted Payment Method	Use only valid, active payment methods for refunds
Payment Dispute Validation	INVALID_REQUEST	400 BAD REQUEST	Payment is in dispute and not available for refund	When attempting to refund a payment that is in dispute	Refunds are not applicable for payments where the merchant has lost the dispute, as the customer has already received the funds through the dispute resolution process.
Refund Already Exists	INVALID_REQUEST	400 BAD REQUEST	This payment is already refunded	When attempting to create a refund on already completed payment	If the payment has already been fully refunded, additional linked refunds are not allowed. To provide more funds to the customer, issue a credit using a valid payment method.
Refund Already Exists (merchantTransactionId)	INVALID_REQUEST	400 BAD REQUEST	Refund already exists for the given merchantTransactionId	When attempting to create a refund with a duplicate merchantTransactionId	Provide a unique merchantTransactionId for every refund transaction

Checkout Session Authorization Error Codes

Location

See details

Error Code Summary

Error Title Reference	Error Title	HTTP Status	Detail Message	Scenario	Resolution
Checkout Session Authorization	FORBIDDEN	403 FORBIDDEN	Access denied when attempting to save payment method using completed session	Attempting to save payment method with a completed checkout session	Create a new session for saving payment methods; completed sessions cannot be reused
	FORBIDDEN	403 FORBIDDEN	Access denied when attempting to save payment method using PAYMENT mode	Attempting to save payment method when session is in payment mode	Use PAYMENT_METHOD_ENTRY or WALLET or PAYMENT_WITH_WALLET mode for saving payment methods
	FORBIDDEN	403 FORBIDDEN	Access denied when attempting to poll setup payment method using PAYMENT mode	Attempting to poll for setup status when session is in payment mode	Use PAYMENT_METHOD_ENTRY or WALLET or PAYMENT_WITH_WALLET mode for saving payment methods
	FORBIDDEN	403 FORBIDDEN	Access denied when attempting to save payment method using cancelled session	Attempting to save payment method with a cancelled checkout session	Create a new session; cancelled sessions cannot be reused
	FORBIDDEN	403 FORBIDDEN	Not allowed to access this session	When merchant2 tries to access a session initiated by merchant1	Use the same merchant credentials that were used to create the session

Config Object Error Codes

Location

See details

Error Code Summary

Error Title Reference	Error & Status	Detail Message	Scenario	Resolution
Config Parameter Validation
saveDisabled/paymentMethodSaveMode not supported in [modes]	INVALID_REQUEST 400 BAD REQUEST	Invalid Request. Request parameter saveDisabled or paymentMethodSaveMode not supported in Mode: [modes]	When sending a request with saveDisabled=true or paymentMethodSaveMode specified, and mode contains fallback-not-possible modes	Remove saveDisabled or paymentMethodSaveMode parameters when using non-supported modes
Payment Method ID required for PAYMENT_METHOD_DISPLAY	INVALID_REQUEST 400 BAD REQUEST	Payment Method ID is required for mode - PAYMENT_METHOD_DISPLAY	When sending a request with PAYMENT_METHOD_DISPLAY mode but omitting the payment method ID	Include a valid payment method ID when using PAYMENT_METHOD_DISPLAY mode
saveDisabled and paymentMethodSaveMode cannot be used together	INVALID_REQUEST 400 BAD REQUEST	Invalid request: 'saveDisabled' and 'paymentMethodSaveMode' cannot be used together. Use only 'paymentMethodSaveMode'.	When sending a request with both saveDisabled and paymentMethodSaveMode specified	Use only paymentMethodSaveMode parameter, not both parameters together
Merchant name contains invalid characters	INVALID_REQUEST 400 BAD REQUEST	config.merchant.name Merchant name contains invalid characters	When the merchant name in the config object contains unsupported characters (only alphanumeric, space, hyphen, and dot)	Use only alphanumeric characters, spaces, hyphens, and dots in the merchant name
Merchant name must not be blank	INVALID_REQUEST 400 BAD REQUEST	config.merchant.name Merchant name must not be blank	When the merchant name in the config object is blank or not provided	Provide a non-empty merchant name in the config object
Merchant name character limit	INVALID_REQUEST 400 BAD REQUEST	config.merchant.name Merchant name must be less than or equal to 80 characters	When the merchant name in the config object exceeds 80 characters	Ensure merchant name is 80 characters or less
Invalid mode	INVALID_REQUEST 400 BAD REQUEST	Invalid mode	When providing an invalid session mode	Use one of the supported session modes (PAYMENT, PAYMENT_WITH_WALLET, WALLET, etc.)
Invalid PaymentMethodChannel	INVALID_REQUEST 400 BAD REQUEST	Invalid PaymentMethodChannel	When providing an invalid payment method channel	Use one of the supported payment method channels
Payment method type is not configured	INVALID_REQUEST 400 BAD REQUEST	Payment method type is not configured.	Payment method type is missing or not configured for the merchant during session creation	Ensure the payment method type is configured for your merchant account
You have no capture methods available	INVALID_REQUEST 400 BAD REQUEST	You have no capture methods available.	No available channels for configured payment methods (e.g., merchant configuration or session error)	Contact support to enable appropriate capture methods for your account
config.privacyPolicyUrl must be a valid URL	INVALID_REQUEST 400 BAD REQUEST	config.privacyPolicyUrl must be a valid URL	When privacyPolicyUrl in config is not a valid URL	Provide a valid, properly formatted URL for the privacy policy
Session Mode not applicable for guest checkout	INVALID_REQUEST 400 BAD REQUEST	Session Mode not applicable for guest checkout!	When a session mode is not allowed for guest checkout (WALLET, PAYMENT_METHOD_SELECT, PAYMENT_METHOD_ENTRY, PAYMENT_WITH_WALLET)	For guest checkout, use only supported modes like PAYMENT or PAYMENT_METHOD_DISPLAY
Invalid Card Category type	INVALID_REQUEST 400 BAD REQUEST	Invalid card category type config.cardCategories.type	When a card categories type is not given as Merchant configured type ( ex: MANUFACTURER_CARD )	Use only merchant-configured card category types
More than 100 medications	INVALID_REQUEST 400 BAD REQUEST	Maximum of 100 medications allowed in cardCategories[].medication	When a card categories medication having a more than 100 medications	Limit medications to 100 per card category
Card Categories given but Medication not provided	INVALID_REQUEST 400 BAD REQUEST	Medications cannot be empty in cardCategories[].medications	When a Card Categories given as Manufacturer card, medication should have to be provided	Provide at least one medication in cardCategories[].medications
More than 100 char in cardCategories.label	INVALID_REQUEST 400 BAD REQUEST	Category label cannot exceed 100 characters	When a Card Categories label consisting more then 100 characters	Limit card category label to 100 characters or less
More than 100 char or empty string in medication.value	INVALID_REQUEST 400 BAD REQUEST	Medication value cannot be empty and maximum allowed length is 100	When a Card Categories medication label consisting more then 100 characters	Provide a non-empty medication value of 100 characters or less
More than 100 char or empty string in medication.label	INVALID_REQUEST 400 BAD REQUEST	Medication label cannot be empty and maximum allowed length is 100	When a Card Categories medication value consisting more then 100 characters	Provide a non-empty medication label of 100 characters or less

Sessions API Error Codes

Location

See details

Error Code Summary

Error Title Reference	Error Title	HTTP Status	Detail Message	Scenario	Resolution
Session Controller Validation
Card WS2 check has failed	INVALID_REQUEST	400 BAD REQUEST	Card WS2 check has failed.	WS2 verification of agent information (e.g., MSID) failed during session creation	Ensure agent userid is part of PCI_WorkStation group
Session Id not found	NOT_FOUND	404 NOT FOUND	Session Id not found	When requesting a session that doesn't exist	Check that the session ID is correct and the session has been created
Your session has been canceled	SESSION_CANCELED	410 GONE	Your session has been canceled	When requesting a canceled session	Create a new session; canceled sessions cannot be reused
Your session is no longer valid	SESSION_TIMEOUT	401 UNAUTHORIZED	Your session is no longer valid	When requesting an expired session	Create a new session; expired sessions cannot be reused
Not allowed to access this session	FORBIDDEN	403 FORBIDDEN	Not allowed to access this session	When merchant ID in request doesn't match the session's merchant ID	Use the same merchant credentials that were used to create the session
Customer Identifier is Missing	INVALID_REQUEST	400 BAD REQUEST	Customer identifier is missing	When customer identifier is not provided for session modes: PAYMENT_METHOD_ENTRY, WALLET, PAYMENT_METHOD_SELECT, PAYMENT_METHOD_DISPLAY	Include a valid customer identifier (hsid, enterpriseId, or metadata)
Consent is required	INVALID_REQUEST	400 BAD REQUEST	Consent is required!	When consent is missing in PAYMENT mode	Include a valid consent object with the required fields
payment is required	INVALID_REQUEST	400 BAD REQUEST	payment is required	When payment object is missing for session modes: PAYMENT, PAYMENT_WITH_WALLET	Include a valid payment object with the required fields