Payment Method Options Object

{
  "id": "ea35b4d0-79fc-461b-84a0-a4e8e64eecd9",
  "card": {
    "captureMethod": "automatic",
    "threeDsMethod": "CHALLENGE",
    "processingConfig": {
      "bankMerchantId": null,
      "merchantIdTag": null
    },
    "installment": null
  },
  "virtualAccount": {
    "channel": "BRI",
    "virtualAccountName": "Reforza Pivot",
    "virtualAccountNumber": "999996",
    "expiryAt": "2025-03-30T23:59:05Z"
  },
  "ewallet": {
    "channel": "DANA",
    "expiryAt": "2025-03-30T23:59:05Z"
  },
  "qr": {
    "expiryAt": "2025-03-30T23:59:05Z"
  }
}

Detail Payment Method Options Object

Parameter	Data Type	Requirement	Description
id	String	O	Identifier for stored preset payment method options
card	Object	O	Cards Payment Options, Mandatory if payment method types selected is CARDS
captureMethod	String	O	If merchant wanted to manually capture, possible values: automatic manual
threeDsMethod	String	O	We will try to provide options for three_ds later, possible values: AUTOMATIC (DEFAULT) NEVER CHALLENGE
processingConfig	Object	O	Only for Facilitator model, to pass the bank MID they want to route this transaction to
>> bankMerchantId	String	C
>> merchantIdTag	String	C
installment	Object	O	Installment Object
virtualAccount	Object	O
channel	String	O	Virtual Account Bank Name, possible values are PERMATA BRI MANDIRI CIMB BNC etc
virtualAccountName	String	O	All Virtual Account Name will use merchant short name For some banks that can perform custom name, this field will be used
virtualAccountNumber	String	O	The corresponding virtual account number that can be used by Customers to send payments to If merchants want to have their custom number they can pass this field
expiryAt	String	M	VA expiration time format YYYY-MM-DDTHH:MM:SSZ
ewallet	Object	O
channel	String	O	Ewallet channel, possible values are DANA OVO SHOPEEPAY
expiryAt	String	M	Payment expiration time format YYYY-MM-DDTHH:MM:SSZ
qr	Object	O
expiryAt	String	M	Payment expiration time format YYYY-MM-DDTHH:MM:SSZ